Bug#835507: Please clarify that sysvinit support decision is not going to expire
>>>>> "Ansgar" == Ansgar Burchardt <firstname.lastname@example.org> writes:
Ansgar> On Fri, 26 Aug 2016 08:50:13 -0400 Sam Hartman wrote:
>> I think we want to reaffirm that policy section 9.3.2 and section
>> represent current policy for init scripts, quoting particularly
>> the following text from section 9.3.2: Packages that
>> include daemons for system services should place
>> in `/etc/init.d' to start or stop services at boot time or
Ansgar> during a
>> change of runlevel.
Ansgar> Does this really represent current policy?
Ansgar> As far as I can tell Policy still assumes that sysvinit is
Ansgar> the default init system and everything else is an "alternate
Ansgar> init system" (9.11).
There are many problems with regard to policy and init systems. I
believe that 9.3.2 on init scripts and 9.3.3 on update-rc.d are still
our current policy and still solid.
The rest of policy in this area really needs to be updated, but if you
see specific problems with those sections, please explain them. I did a
complete review this morning and they seemed fine to me, especially if
you take more of an RFC 2119 interpretation of SHOULD than we
classically have admitted we take in policy.