Bug#162120: debian-policy: Deletion of configuration files--should it be preserved?
Anthony Towns <aj@azure.humbug.org.au> writes:
> Really? What is it? I only saw comments that amount to "I interpret
> policy this way" and "other things do it this way", neither of which is
> a response to my original request for "someone to give a good reason why
> randomly deleting config files of installed packages is the best way to
> go about things, and should be supported."
I didn't say that it was the best way to go about things; even Manoj
didn't say that. Still, users who read the current policy document
might be misled (at least two people, one of the Manoj, have read the
policy to be contrary to what you want). So, if the packages aren't
going to be changed, then policy should be.
> Well, I suppose I could change the scripts to cope, and change inetd to
> just enable all its internal services unless told otherwise, so anyone
> who was stupid enough to think removing the config file would do any
> good could get their machine DoS'ed off the .net thanks to a handful of
> untracable spoofed packets. Because, hey, personal whims, and the letter
> of policy are what matters, not the needs of our userbase, right?
No, a perfectly reasonable alternative would be to change policy to
match. I don't care which alternative is chosen.
Thomas
Reply to: