| 1 |
Neil Bothwick wrote: |
| 2 |
> On Tue, 31 May 2011 23:43:59 +0100, David W Noon wrote: |
| 3 |
> |
| 4 |
> |
| 5 |
>> Remember that I am writing purely about *unmerged* packages. In the |
| 6 |
>> case of a rebuild or upgrade, customizations would be preserved just |
| 7 |
>> as they are now. |
| 8 |
>> |
| 9 |
> Sometimes it is necessary to unmerge a package before emerging a newer |
| 10 |
> version, either manually or by portage, to resolve blockers. Making |
| 11 |
> unmerge remove all config files would cause breakage in such a case. |
| 12 |
> |
| 13 |
> There's a reason why the CONFIG_PROTECT variable is so named. |
| 14 |
> |
| 15 |
> |
| 16 |
> |
| 17 |
|
| 18 |
I had thought of something like that being done manually but didn't |
| 19 |
think of portage doing it itself. That's a better reason than mine even |
| 20 |
tho it does the same thing. |
| 21 |
|
| 22 |
Dale |
| 23 |
|
| 24 |
:-) :-) |
Archives