Hello everyone, Since I myself and some others had some criticisms and/or doubts of Adam Borowski's proposal, I would like to propose a different one. With this I hope to:
* make new installations use systemd-sysv (with no reliance on undefined or inconsistent behavior from the various ways of setting up a Debian install or chroot) * make current installations that have sysvinit stick with it * allow for the automatic switch from sysvinit to systemd-sysv in stretch, buster, or another later release So, the change would be that: the sysvinit package would cease being a transition / shim package, however it would not signal that a user explicitly installed sysvinit; sysvinit-core would be a simple package that just depended on sysvinit, and the presence of this package *would* signal that the user explicitly installed sysvinit; init would (pre-)depend on "systemd-sysv | sysvinit | sysvinit-core | upstart". If an automatic switch is something that the project wants, but after Jessie, then then the init dependency would be changed to "systemd-sysv | sysvinit-core | upstart". Cheers, -- Cameron Norman -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org