On Wed, 1 Jun 2011 15:57:58 +0100, David W Noon wrote: > >No it's not. You were referring to a special case of the general > >statement I made. > > I can see no material difference in the two statements in question, > unless you mean "by the user" is a special case. By whom else would > files be modified externally to Portage?
I mean that your referring to config files is a special case, portage won't remove any file from anywhere in the tree that has been modified. > The contents of the file have been modified, but the file itself is > still owned by the package. That depends on your definition of ownership. The file is not the same file that portage installed, so it can no longer claim ownership, that is now down to whoever modified the file. > That's why etc-update, cfg-update, etc., > check any new version of the file when the package is upgraded: the > file is still owned by the package. No, portage is checking whether a config file of the same name as the one installed by the package exists. It doesn't care where the existing file originated, only that it is in a CONFIG_PROTECTed directory and should not be overwritten. etc-update and friends simply look for ._cfg* files. > >A customised file contains an investment of the user's time, a generic > >file does not. That investment may be small or great, but it is not > >for portage to determine that value and remove the file without the > >user's consent. > > How much is that investment worth when the entire package is being > deleted? That depends on whether the package will be installed again. > Remember: we are discussing the COMPLETE DELETION of a > package, not an upgrade or rebuild. We are discussing unmerge behaviour, unmerging is part of the upgrade and rebuild processes. > >We agree on the usefulness of a purge-like option but not on the > >desirability or otherwise of the current default behaviour > > I called it an "annoyance". Having to clean up obsolete configuration > files is just that, unless you can offer a better term. How about "feature request waiting to be made"? -- Neil Bothwick If at first you don't succeed, call in an airstrike.
signature.asc
Description: PGP signature
