Bug#727708: multiple init systems - formal resolution proposal
2014-01-29 Adrian Bunk <bunk@stusta.de>:
> [...]
> I do fully acknowledge that there are issues with ConsoleKit being
> unmaintained and many non-systemd codepath in GNOME being unmaintained
> and with GNOME missing some non-basic functionality without systemd.
>
> But claims that even basic functionality in GNOME in jessie could not
> work without logind might just be FUD.
>
> The TC can rule that systemd will be the default for jessie and that
> dependencies on systemd will be OK if a maintainer wishes do add them,
> but such a decision should be based on facts and not on unproven
> "GNOME needs it" claims.
No, Josselin is right: GNOME *does not* work without services provided
by systemd. He never said that - given some amount of work - it can't
be made working. But given the limited resources of the GNOME team, I
can fully understand why they don't want to make the other solutions
work (e.g. by taking over ConsoleKit maintenance).
So, Joss' statement is correct.
Also, have in mind that logind provides the basis for some additional
features (e.g. real multiseat-support, sane closing of applications on
logout, shutdown inhibitions etc.) and that systemd/logind is required
for using Wayland, and GNOME is definitively going that road. Also,
there are plans to make systemd --user manage a GNOME session, so the
gnome-session codepath wil bitrot soon as well. And even on KDE we are
evaluating that option[1], so it's not just GNOME going that way.
Cheers,
Matthias
[1] Fallbacks in place, but I don't know anyone who likes working on startkde...
--
Debian Developer | Freedesktop-Developer
I welcome VSRE emails. See http://vsre.info/
Reply to: