Hi! Please may I suggest another option for consideration: a commitment to support two chosen init systems. On mainstream ports (Linux amd64, i386) where two init systems are available, a package should be tested and made to work reasonably well on both. Any port would have at least one of these init systems. This offers users a choice to avoid a particular init system, try the new features in another one, or perhaps stay with what they already have. It would require work, but maybe this turns argument into something that can be accomplished through team effort. Supposing systemd and sysvinit were chosen: * systemd folks would aim to make best use of the existing sysvinit scripts, and provide help to packages where improvement can be made; * sysvinit users and porters can help ensure things keep working there. I've begun a debate page here, more suggestions are welcome: https://wiki.debian.org/debate/initsystem/multiple or follow up on debian-devel@ Thanks! Regards, -- Steven Chamberlain steven@pyro.eu.org
Attachment:
signature.asc
Description: OpenPGP digital signature