according to man portage, one can have a /etc/portage/package.keywords (or use, mask, unmask). All files within that directory are pulled together and then treated as one package.keywords file. This is a really cool approach so I can easily distribute sections of my package.keywords file to others. The only problem I see here is, that you have to move the file packages.keywords away, create a directory with the same name and then move the original file into that directory. I'd find it much better if we could just keep the file and make a directory packages.keywords.d so when someone would like to try my configs, he's not scared away by my script that's messing around with some of his most important files. Currently, that would be: mv /etc/portage/package.keywords /etc/portage/package.keywords.file mkdir /etc/portage/package.keywords mv /etc/portage/package.keywords.file /etc/portage/package.keywords/ wget -P /etc/portage/package.keywords http://example.com/my-special-keywords better would be the following, which is not touching the original package.keywords at all mkdir /etc/portage/package.keywords.d wget -P /etc/portage/package.keywords.d http://example.com/my-special-keywords Reproducible: Always Steps to Reproduce: mkdir /etc/portage/package.keywords ;-)
I used the same name on purpose: a) the code is easier to maintain this way b) we avoid the question how package.keywords and package.keywords.d should be ordered c) IMO having two locations would just increase the confusion Also the problem you're pointing out is a one time thing, not something people have to do regulary.
Well I was pretty surprised to see you can also have a directory instead of a file and I guess not many people know about that or even use it -- so I still consider it a useful proposal.
