Roger Leigh wrote: > ignored them when dependency-based boot was in use. For wheezy in > practice it will always ignore them since dependency-based boot is > required. In jessie we removed start and stop entirely; they still > exist internally, but are just aliases for "defaults", and issue a > warning if used; all runlevel information is obtained from the LSB > headers. > > It would be great if dh_installinit could stop calling update-rc.d > with start or stop arguments, but initially just warning if the > params contains "start" or "stop" arguments would be a good first > step. I'm not sure of whether it's practical or not to just pass > "defaults" if "start" or "stop" are detected--I imagine there might > be complications, so just warning might be better?
I am uncomfortable with debhelper commands parsing parameters passed after -- and producing warnings for two reasons: 1. It's an abstraction violation for it to look at those parameters. 2. Debhelper's job is not to produce lots of verbose warnings about things possibly wrong with the package it's building. If update-rc.d no longer has any options which it makes sense to be propigated from dh_installinit then it could stop sending the -- options to it at all. I'm not sure if the disable|enable option could make sense to be used. > I'll also look at getting lintian warnings added which should be > able to pick up dh_installinit and update-rc.d usage and also warn. That seems much more appropriate. -- see shy jo
signature.asc
Description: Digital signature
