I would like to see support for package.accept_keywords in profiles as discussed in bug #55321
With the current method of using package.keywords, it's easy to accidentally unmask packages normally masked by missing keywords (eg. -9999 live packages) without realizing it (the affected package versions may not exist when the profile is created)
Yeah, that would be a very good feature for my profiles.
Right now I have to use ugly hack that walks the profiles and regenerates package.keywords after every change.
This is in git now:
This is in 2.2_rc68, but I'll leave this bug open until it's in an unmasked version.
This is fixed in 2.1.9.
Could someone please explain what you use this file for? More specifically, what you are able to do with it that you can't do with package.keywords.
Comment #0 talks about not accidentally keywording live ebuilds, but those should be masked by package.mask anyway.