> I'm so happy to see you continue to dig into antiX's plumbing. Isn't it an
absolutely wonderful conceptual approach?
I was initially thrown off by the [1][nosystemd repository], which currently
contains a single package, but used to contain a large number of packages
that were no longer actually needed or used in antiX. The key is that
starting with version 241 elogind is ABI compatible with libsystemd0, meaning
that it works as a drop-in replacement with no need to recompile packages
that have been compiled against libsystemd0. Unfortunately elogind 241
missed the window to make it into Debian buster, which has elogind 239, but
antiX backports [a newer version][2]. Basically, these packages
* eudev
* elogind >=241
* [libpam-elogind-compat][3]
* sysv-rc
can replace systemd and leave Debian otherwise functional, barring the
occasional missing init script, which [sysd2sysv][4] makes relatively easy to
create from a systemd unit file.
> I did not know that Devuan was wasting time removing those references.
That's an interesting point, I'm going to need to explore further.
Maybe my "wasting time" comment was unfair. I don't know how much time they
actually spent on it or whether or not it's a bottleneck in development.
[Here's a pretty typical example][5] though. Debian's lightdm package works
fine with or without systemd. Devuan's changes just remove systemd support.
This has no benefit for non-systemd users, which presumably includes all
Devuan users.
[1] http://repo.antixlinux.com/buster/pool/nosystemd/
[2]: http://repo.antixlinux.com/buster/pool/main/e/elogind/
[3]: https://packages.debian.org/experimental/libpam-elogind-compat
[4]: http://www.trek.eu.org/devel/sysd2v/
[5]:
https://git.devuan.org/devuan-packages/lightdm/commit/f57ed155705a5b41a1879057e2a8b50ae1d6394f
