11 ms·
Which packages had a hard systemd/logind requirement upstream? As far as I understand it, GNOME still gets upstream patches from BSD developers and is still sup
by cycloptic 6y ago
Which packages had a hard systemd/logind requirement upstream? As far as I understand it, GNOME still gets upstream patches from BSD developers and is still supported there. (Some Debian packages do have hard dependencies on systemd, but this is a downstream packaging issue)
- jasonjayr 6y agoI don't want to leave my hearsay uncited, but try here: https://blogs.gnome.org/ovitters/2013/09/25/gnome-and-logindsystemd-thoughts/ https://blogs.gnome.org/ovitters/2013/09/25/gnome-and-logind... Slightly more recently: https://digitizor.com/gnome-linux-only/ https://digitizor.com/gnome-linux-only/ This was an eternity ago in internet time, and I'm not all up and up on BSD development, but maybe enough folks are keeping it going on BSD nowadays?
- cycloptic 6y agoInteresting, I checked and the only upstream component of GNOME I could find that requires systemd and doesn't have a compile flag for it is gdm. This isn't required to start GNOME (you can use any other display manager) and FreeBSD/OpenBSD seem to be maintaining consolekit patches for it downstream. So I see why there is little incentive to fix this upstream. (On non-systemd Linux distros the focus has shifted to staying compatible with elogind, but that doesn't work on BSD)