On Thu, 2 Apr 2015 11:29:33 +0200, Róbert Čerňanský wrote: > > Portage doesn't change your package.use file, it creates a new one > > using the standard CONFIG_PROTECT process. Then you use etc-update or > > similar to view and verify the changes. > > What I am trying to tell is that portage manages its stuff (USE > dependencies), through you, in your configuration files. It is nice > that it does not overwrite them directly without asking ;-) but in the > end the content ends up there one way or other. Portage should have > its own internal database for USE deps and manage it like it manages db > of standard package dependencies.
I'm coming round to that way of thinking too. I was simply pointing out that the autounmask feature doesn't clobber existing configs, so people weren't put off using it by the implication that it did. A mechanism for portage to manage this outside of /etc/portage would help separate portage's decisions and requirements from those of the user -- Neil Bothwick X-Modem- A device on the losing end of an encounter with lightning.
pgpIRrltMCImj.pgp
Description: OpenPGP digital signature
