[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: systemd effectively mandatory now due to GNOME

On 25 October 2013 06:37, Russ Allbery <rra@debian.org> wrote:
I'm missing a key bit of context here.  Does gnome-settings-daemon just
require that systemd be installed?  Or does it require that the init
system be systemd?

Me too. Am getting rather lost as to why gnome-settings-daemon depends on systemd.

Can somebody please confirm my understanding:

* Gnome upstream in no way requires systemd. I would assume it can take advantage of it.If no systemd you loose support for some features.

* In Debian, the latest Gnome packages requires gnome-settings-daemon, which does require systemd. However systemd doesn't actually need to be running as initd.

* The gnome-settings-daemon package due to {build options, runtime options, Jedi council decision} requires a/an {systemd shared libary, systemd binary executable, systemd dbus implementation, chocolate biscuit, coffee} and if not available at run time then {you loose support for extra features, gnome breaks, life on the planet will cease to exist}. (*cross out incorrect options)

* Ubuntu has a patch to fix the above, however it is is prone to break with new versions of systemd (???) and nobody has volunteered to continue to support it.

* The Debian packages of Gnome currently will not install on non-Linux systems.

* Discussion starts on debian-devel mailing list with lots of pointing of fingers.

* I blame Tux. Tuz said so.
Brian May <brian@microcomaustralia.com.au>

Reply to: