Re: strange portage behaviour

Alin Năstac wrote:
> Portage no longer install ._cfg0000_* files for the CONFIG_PROTECTed
> files touched by the user. Even if I remove the package and reinstall it
> again, the protected file will remain like it is.
> 
> Can someone enlighten me?
> 

It's common for people get get confused like this by the "confmem"
behavior that's built into portage's merge process. You can use
--noconfmem to disable it.

In newer versions of portage (those not marked stable yet),
uninstalling a package or downgrading it will automatically trigger
behavior like --noconfmem [1], so hopefully this will help to avoid
some confusion in the future.

Zac

[1] http://sources.gentoo.org/viewcvs.py/portage?rev=10250&view=rev