On Sat, May 12, 2012 at 08:04:15PM +0300, Anton Zinoviev wrote: > On Sat, May 12, 2012 at 07:01:20AM -0700, Steve Langasek wrote: > > No, you absolutely do *not* need this. The policy rule isn't "on purge, > > remove all config files if the admin hasn't edited them", it's "on purge, > > remove *all configuration files*". > All configuration files owned by the package. This is not an interesting distinction. > There is no way to tell whether a file in /etc/console-setup is owned by > the package console-setup or it has been put there by the admin and is > unrelated to console-setup. Who cares? If the admin is putting files in a directory named "/etc/console-setup" that are *unrelated to console-setup*, there's no reason to coddle them by making the console-setup's maintainer scripts more complex. And most package maintainers have not bothered to implement such handling. So an admin who hasn't yet learned the lesson to not put random files in unrelated directories under /etc will have plenty of opportunities to learn it before purging such a basic package as console-setup. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slangasek@ubuntu.com vorlon@debian.org
Attachment:
signature.asc
Description: Digital signature