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

Bug#361137: [PROPOSAL] Make use of invoke-rc.d, if available, mandatory

Lars Wirzenius <liw@liw.iki.fi> writes:

> Package: debian-policy
> Severity: wishlist

> Given that the initial reactions to this were uniformly positive, I'll
> need to actually start following procedure and use the BTS.

> The formal proposal is to change ("Running initscripts"), second
> paragraph, from this:

>         The use of invoke-rc.d to invoke the /etc/init.d/* initscripts
>         is strongly recommended[51], instead of calling them directly.

> to this:

>         The use of invoke-rc.d to invoke the /etc/init.d/* initscripts
>         is mandatory if it is installed.


> Because invoke-rc.d is in a package (sysv-rc or file-rc) that an
> essential package depends on, it is guaranteed that invoke-rc.d is
> always on the system. In principle, we could then strike the four last
> words of the proposed paragraph, which would simplify things for
> packages. I am unsure of whether we should make invoke-rc.d's
> essentialness more explicit in that case.

I'd kind of like this since it would make the lintian check easier if it
didn't have to deal with the logic to call the init script directly if
invoke-rc.d doesn't exist, but I haven't looked into what this means when
it comes to init handling systems.

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

Reply to: