Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
<p><br>
On May 31, 2011 3:02 AM, "Neil Bothwick" <<a href="mailto:neil@...">neil@...</a>> wrote:<br>
><br>
> On Mon, 30 May 2011 23:08:08 +0100, David W Noon wrote:<br>
><br>
> > You have just touched on an annoyance of unmerge, in that it does not<br>
> > clean up configuration files that have been modified. It removes files<br>
> > that are still in the same state as when the package was emerged, but<br>
> > not those modified by the user. I don't see how user changes make the<br>
> > file more important than would be in its vanilla state.<br>
><br>
> It doesn't remove *any* files that have been modified, the reasons<br>
> systems used to get cluttered with orphaned .la files. The logic is quite<br>
> simple, if it is not the file portage installed with the package, it<br>
> should not be uninstalled with the package. There are times when some<br>
> sort of --force-remove option to remove both these and files in<br>
> CONFIG_PROTECTed directories would be useful.<br>
><br>
If you want to ensure that portage removes a configuration file then add CONFIG_PROTECT_MASK="/etc" to the unmerge line and portage will remove the configuration files as well.</p>
<p>James Wall <br>
><br>
> --<br>
> Neil Bothwick<br>
><br>
> Format: (v.) to erase irrevocably and unintentionally.<br>
> (n.) The process of such erasure.<br>
</p>
|
|
