On 08 Jul 2003 10:42:25 +0200 Thomas Hood <jdthood@yahoo.co.uk> wrote: > The proposal is that policy explicitly permit what is > already done by some packages -- namely, the regeneration > of configuration files that have been deleted. This seems > sensible. This clause will serve as a warning to administrators > that deleting configuration files may not have the effect > that they expect. > > It would also be helpful to say that if an administrator > wishes to prevent the regeneration from happening then > he should empty the file, not delete it. > > A counter-proposal from Manoj Srivastava was (explicitly?) to > forbid the regeneration of configuration files that have been > deleted, but this was shot down by AJT in no uncertain terms. I'm new to the bug, but I've read through the log. I have no objection against ammending Policy to be wishy-washy about what happens when the admin deletes config files - obviously there *are* times when they should be regenerated (I don't believe the examples given [/etc/passwd and /etc/inetd.conf] are particularily good, but nevertheless). That being said, any package which doesn't clearly document that they regenerate deleted configuration files in a prominent place in README.Debian will be getting a bug report (probably with a patch ;).
Attachment:
pgp1nXceD1L34.pgp
Description: PGP signature