On Thu, Aug 19, 2004 at 07:07:24AM -0600, Wesley J Landaker wrote: > On Thursday 19 August 2004 03:50, Richard Kettlewell wrote: > > Steve Greenland <steveg@moregruel.net> writes: > > Perhaps life would be improved by having a way to easily discover > > what --purge would remove without actually running it (or reading the > > relevant maintainer script). You already get this for conffiles, > > which are a subset of the answer; it could be extended to other > > things removed by --purge. > > It seems like 'dpkg --dry-run --purge package' would be a great place > for this to happen. Currently, it just says: That would require somehow knowing that every maintainer script will honour such a request before doing the "dry run", retrofitting that would suck pretty hard. Policy versions might be a help, but I'd be a bit twitchy about it. Either that or more metadata needs to be stuffed into every package saying exactly what it will do at various stages for dpkg to process. It would be kinda cool on occasion, but I think the current rule is practically sufficient -- remove makes the package inoperative by deleting the "static" parts of a package, purge should get rid of all traces of the package from your system. Leaving a few config files around when you want to keep the logs doesn't seem like a massive problem to me. - Matt
Attachment:
signature.asc
Description: Digital signature