Sometimes we (arch teams) need to mask a use flag on just ONE package but it is not acceptable to mask it for every package. For example, we'd like to mask use flag 'foo' in 'some-cat/bar' because it brings a broken dependency on our arch, however, masking 'foo' for the whole tree is not acceptable since it works for the rest of the packages. So we can't use use.mask. We would like to have a way to mask use flags for just the package we want from our profiles. Thanks, Ferdy
*** Bug 128593 has been marked as a duplicate of this bug. ***
I *had* the impression a bug was open already but I forgot which one it was :P
So, KingTaco is so keen to tell he'll be taking a look to this ;)
Perhaps we could support both package.use and package.use.mask at the repo and profile levels. The two would be complimentary and the extended support for package.use would be more flexible than the "default iuse" patch that has been proposed.
per profile/repo package.{use,keywords,unmask} might become quite confusing when it comes to priorities.
(In reply to comment #5) > per profile/repo package.{use,keywords,unmask} might become quite confusing > when it comes to priorities. That's the case with any kind of stacking. The stacking behavior certainly needs to be well documented. In addition, we can provide some way to dump debug information in case we (or a user) needs to troubleshoot the stacking. Actually, today in #gentoo-portage, ferringb mentioned that the functionality of package.use.mask can acutally be represented via package.mask + use deps. Since package.mask is already supported at the profile level, we would only need to add the additional use deps support to it.
In svn r4151 I've added support for package.use.mask in the profile. It should behave exactly as use.mask currently does except that it allows USE flags to be masked for specific packages rather than for all packages.
This has been released in 2.1.1_pre4-r3.