On Mon, Oct 28, 2013 at 05:22:14PM +0000, Wouter Verhelst wrote: > On Sat, Oct 26, 2013 at 11:20:21AM -0700, Steve Langasek wrote: > > Right. Whichever init system we pick, I do expect the next step to be to > > drop the requirement to maintain sysvinit backwards-compatibility; > While I'm not sure from your mail whether you meant to suggest otherwise, > I do think that whatever we decide for jessie, we should continue the > requirement of sysvinit compatibility for at least one release after we > ship with some more modern init system. The point was not about whether the init system would maintain backwards-compatibility with sysvinit, which is straightforward to conserve for some time, but whether individual packages providing services need to maintain compatibility with sysvinit or if they can adopt the native service definition format. If we adopt a different init system as the default in jessie, then certainly by jessie+1 at the latest, maintainers should feel free to use the native format exclusively and not feel required to maintain compatibility with sysvinit. > Also, since all alternative init implementations under consideration do > support sysv-style init scripts, I think that whatever init system we > (well, you, the TC) end up choosing, the requirement in policy should be > that a package should ship either some init configuration for the > default init system, or a sysv-style init script. In fact, I think we > should continue to encourage the latter, in cases where it does make > sense (e.g., when a given daemon doesn't have any init system specific > features that could be enabled), since that will help our non-Linux > ports without significantly impacting performance of the new init > system. I see no reason that, if upstart were chosen as the default, porters could not use it for our non-Linux ports as well. This is a much better outcome across our distribution as a whole than to require developers to continue maintaining init scripts just for our non-Linux ports. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slangasek@ubuntu.com vorlon@debian.org
Attachment:
signature.asc
Description: Digital signature