Bug#601455: Standardize how to disable an init script
Andreas Henriksson <andreas@fatal.se> writes:
> On Sun, Jan 01, 2017 at 10:38:02PM -0800, Russ Allbery wrote:
>> This is mostly just documenting update-rc.d disable in Policy, except
>> that we need to document how to keep a service from ever being enabled
>> and started by installation of a package by doing something to the
>> system *before* the package is installed. This is very important for,
>> say, build environments and other bootstrapping environments. (And we
>> have a mechanism now for this, namely policy.d; it's just not
>> documented in Policy.)
> Since policy still hasn't caught up with anything except init scripts
> and this still having sharp edges left (in real life, not policy) even
> after all this years I was under the impression that this would
> basically get outsourced into the practical sphere and not be in policy
> for long time to come.
> Thanks for the feedback.
Well, there are many, many things that should be in Policy but aren't.
But I like to keep the bugs open anyway, even if no one is currently
actively working on it, because the work *does* need to get done at some
point.
> Also see https://bugs.debian.org/709384 for discussion on how to
> implement this right, so policy can get it right before dh_installinit
> does. ;)
Yeah, it's high on my to-do list to look over the various pending fixes to
the Policy discussion of init systems, since the whole thing is massively
out of date at this point and, unlike with multiarch and triggers, is
documenting things that are actually wrong instead of just missing
documentation of new things.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: