Simon McVittie <s...@debian.org> writes: > I don't think a bug against the "general" pseudo-package is going to > solve this. If you think Policy should explicitly state it, I would > suggest opening a bug against Policy (or possibly reopening and > reassigning #601455); or if you think it's a bug already, please open > bugs in individual packages that have it (the original bug reporter > noted mpd and icecast2).
If Policy says anything, I suspect we'll say that having a disable flag in /etc/default is considered harmful and packages should instead document that update-rc.d disable should be used for this purpose (and perhaps migrate the disabled flag to update-rc.d disable on upgrade). > If we continue to support sysvinit (even if it's as one of several > alternatives), I think we should promote something like "update-rc.d foo > disable" as the "official" way for a sysadmin to disable init > scripts. Disabling things via /etc/default/foo should be deprecated, and > only kept available for backwards compatibility in packages that already > have it (if at all), because it's so easy to get it wrong like this. Yes. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ppp5rfiu....@windlord.stanford.edu
