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