Bug#727708: multiple init systems - formal resolution proposal
Matthias Klumpp dixit:
>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
Hum, we can always add “remove GNOME (3) from Debian” to the
list of GR or TC points to consider (this *has* been suggested
earlier, even)… and given that MATE seems to have picked up
the market of GNOME…
>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,
This is more of a threat than a promise.
>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.
As long as it’s still evaluating… the evaluation can result in
“let’s do a more sane thing, after all GNOME got kicked off Debian
for requiring systemd”.
I *still* don’t see a problem with keeping sysvinit with sysv-rc,
which I’m not overly fond of but which is still better than the
alternatives – and all packages have sysvinit scripts already
*anyway* so there is no added maintenance burden except for those
who do wish to support other inits, which, in turn, can run the
existing initscripts. My favourite option would thus be to keep
sysvinit/sysv-rc forever, keep it as default for jessie, and do
not permit any package to depend on an init implementation, but
allow packages to degrade if the currently active init (be it
the default init or not) does not support everything needed (i.e.
no “allow degrade iff a default init is chosen” or “allow degrade
iff a non-default init is chosen”).
bye,
//mirabilos
--
13:37⎜«Natureshadow» Deep inside, I hate mirabilos. I mean, he's a good
guy. But he's always right! In every fsckin' situation, he's right. Even
with his deeply perverted taste in software and borked ambition towards
broken OSes - in the end, he's damn right about it :(! […] works in mksh
Reply to: