It would greatly ease my maintainer-ship of ebuilds if I had the ability to do something like "xfce-base/* ~amd64" in package.keywords. This would eliminate one step of my process. Alternatively, it was suggested to use @set syntax in package.keywords (which requires bug 244366 to be implemented) because you can make a set per category with something like: 15:12 < Arfrever> darkside_: FYI, the following code can be used to generate set for each category: 15:12 < Arfrever> [categories] 15:12 < Arfrever> class = portage.sets.dbapi.CategorySet 15:12 < Arfrever> multiset = true 15:12 < Arfrever> name_pattern = ${category} However, I still think the original proposal would be more convenient from the user POV too. Please consider.
This is in git now, in these 2 commits and everything in between: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=4f18b95298423b28691f43911632d5d34f69fc84 http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=29825ae82a3a7c51be0b3312e74c9cb0288abbaa
This is fixed in 2.1.9.
