Re: Packagers wanted!
Reply #60 –
It depends on the package. Some arch packages abusively depend on [lib]systemd, others use systemd-related configure options. For the latter, a --disable-systemd flag is usually enough to have them cleaned. The former sometimes can be cured by depending them on [lib]elogind.
Take the dbus diff for example, which is harder to keep clean and needs an additional patch:
--- dbus.arch 2019-02-07 21:33:25.010297658 +0200
+++ dbus.artix 2019-02-07 21:34:12.640308698 +0200
-depends=(libsystemd expat audit)
+depends=(libx11 libelogind expat audit)
-makedepends=(systemd xmlto docbook-xsl python yelp-tools doxygen git autoconf-archive graphviz)
+makedepends=(elogind xmlto docbook-xsl python yelp-tools doxygen git autoconf-archive graphviz)
+ patch -Np 1 -i ${srcdir}/dbus-enable-elogind.patch
+ --with-system-pid-file=/run/dbus/pid \
+ --with-console-auth-dir=/run/console/ \
+ --enable-inotify \
+ --without-systemdsystemunitdir \
+ --disable-systemd \
- --disable-static \
- --without-x
+ --enable-elogind \
+ --enable-x11-autolaunch \
+ --disable-static
Most packages, however, are way easier to maintain as, thankfully, don't really need or want systemd to work.