Bug#727708: multiple init systems - formal resolution proposal

[Ian Jackson <ijackson@chiark.greenend.org.uk>]

Russ Allbery writes ("Bug#727708: multiple init systems - formal resolution proposal"):
> Ian Jackson <ijackson@chiark.greenend.org.uk> writes:
> > I hereby propose the following resolution:
> >    1. Support for sysvinit is mandatory in jessie.
> 
> I agree with this in principle, but I think this loses quite a bit of
> nuance and is likely, phrased in that way, to be used as a stick to beat
> maintainers with in ways that aren't helpful.  I'd rather wait until we
> decide what the default will be and then try to work out exactly what sort
> of sysvinit support we want given that.  The details of any future support
> plan are going to vary.

I am not willing to wait.  I think it is too important to make this
clear right away.  Otherwise the main default decision risks a
stampede to create "facts on the ground".

> >    2. Debian intends to support multiple init systems, for the
> >       foreseeable future, and so long as their respective communities
> >       and code remain healthy.  Nothing outside of an init system's
> >       implementation may require a specific init system to be pid 1.
> 
> I will probably be voting against this.  [...]

I take it then that you have no wording changes which would change
your mind.

Ian.