On 16 October 2014 22:13, Ansgar Burchardt <ans...@debian.org> wrote:
> Aigars Mahinovs <aigar...@debian.org> writes:
>> We have all kinds of policies about what is fine in a package and what
>> is a Release Critical bug. That is a big part of what makes a
>> distribution. This simply adds - "must be able to work with any init
>> system running at PID 1" to those requirements.
>
> No, it does not mean packages have to work with *any* init system. It's
> specifically aimed against a specific init replacement, see [1].
See, there is a clear difference:
* if your software works the same regardless of what process started
it up - that is fine. (Even if you just provide a convenience start-up
script just for one init system.)
* if your software only works if started by this one init system -
that is a problem.
The requirement is that software should be able to work regardless of
how it is started - by systemd, by sysvinit, by other init system or
by a plain shell script called from the "init=" kernel parameter. If
there are any dependant services, those should be also able to be
simply startable by anything. All software in previous Debian releases
satisfied this requirement, so there wasn't even any need to consider
adding such requirement to the policy.
--
Best regards,
Aigars Mahinovs mailto:aigar...@debian.org
#--------------------------------------------------------------#
| .''`. Debian GNU/Linux (http://www.debian.org) |
| : :' : Latvian Open Source Assoc. (http://www.laka.lv) |
| `. `' Linux Administration and Free Software Consulting |
| `- (http://www.aiteki.com) |
#--------------------------------------------------------------#
--
To UNSUBSCRIBE, email to debian-vote-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/CABpYwDXLb9vm_xR=cux2rhkz5ei4bbfarss7wfrtqvvnr3v...@mail.gmail.com
