1 |
On Tue, 31 May 2011 07:34:22 -0500, James Wall wrote: |
2 |
|
3 |
> > It doesn't remove *any* files that have been modified, the reasons |
4 |
> > systems used to get cluttered with orphaned .la files. The logic is |
5 |
> > quite simple, if it is not the file portage installed with the |
6 |
> > package, it should not be uninstalled with the package. There are |
7 |
> > times when some sort of --force-remove option to remove both these |
8 |
> > and files in CONFIG_PROTECTed directories would be useful. |
9 |
> > |
10 |
> If you want to ensure that portage removes a configuration file then add |
11 |
> CONFIG_PROTECT_MASK="/etc" to the unmerge line and portage will remove |
12 |
> the configuration files as well. |
13 |
|
14 |
That will only remove unmodified files, and to do that fully you need |
15 |
CONFIG_PROTECT="-*". Portage doesn't remove any files that have been |
16 |
modified since installation, whether they are in CONFIG_PROTECTEed paths |
17 |
or not. |
18 |
|
19 |
|
20 |
-- |
21 |
Neil Bothwick |
22 |
|
23 |
Did you know that eskimos have 17 different words for linguist ? |