On Sat, Feb 1, 2014 at 6:35 PM, Russ Allbery <r...@debian.org> wrote: > > I *like* systemd, and I would still be very unhappy > if a routine aptitude upgrade (or even a dist-upgrade) of a system > currently running sysvinit suddenly resulted in running systemd without > some sort of critical debconf question or the like. >
In my mind, the package to change init systems would still be separate from its respective init systems. So gnome would depend on org-freedesktop-login1, and the default provider for that virtual package would be (a) a systemd-shim like package if the default debian init system is not systemd or (b) systemd and init-systemd (changes the init line) if systemd is the default. Obviously, if the user has systemd *and* init-systemd installed already, logind would be provided by that. > Maybe we can handle this by having a package that changes the default init > system but have it throw a critical debconf prompt and fail to install if > installed noninteractively. > I undeservedly thought this was a given. Thanks for the thoughts, -- Cameron Norman
