[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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.

>    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 don't think it makes sense to
constrain what we put in the archive in quite this way, as was previously
discussed on this bug.  If some piece of software has no upstream support
for other init systems, I would rather have that software packaged for the
init system that it does support than not permitted to be in Debian at
all.

Major packages or packages with higher than optional priority are possibly
another matter, as possibly are packages which work fine with other init
systems but whose maintainers don't want to add support, but I think
making this sort of flat statement is too constraining.

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>


Reply to: