Re: Make use of invoke-rc.d, if available, mandatory?
Lars Wirzenius <firstname.lastname@example.org> writes:
> Current policy states in section 18.104.22.168 ("Running initscripts") the
> following: "The use of invoke-rc.d to invoke the /etc/init.d/*
> initscripts is strongly recommended, instead of calling them
> Footnote 51 further says: "In the future, the use of invoke-rc.d to
> invoke initscripts shall be made mandatory. Maintainers are advised to
> switch to invoke-rc.d as soon as possible."
> I propose that the future has arrived.
> I ran the attached script on all binary packages in sid/main/i386, and
> it reported 134 packages that I then analyzed manually. There were only
> two false positives (both mentioned how to run their init.d script in a
> message to the user, but didn't run it themselves). All other reported
> packages were true positives. I have attached the list as well.
> Almost all of the packages in the list are either dict-* packages
> (seemingly from the same template), have code from an old debhelper
> version (so a rebuild might suffice), or are otherwise pretty easy to
> fix. Even though the number of packages are fairly large, it is my
> opinion that it should be possible to keep the transition period quite
> short, weeks at most, and I'm willing to put some time into it.
> See also bug #353659 against lintian to add a check for this.
Sounds good to me. This check is also in the lintian Subversion
repository and will be in the next release of lintian.
Russ Allbery (email@example.com) <http://www.eyrie.org/~eagle/>