The file '<overlay>/profile/package.accept_keywords' contains the following line: =category/package-version::repo ~arch When I try to 'emerge -p =category/package-version::repo', I am given the message that a keyword change is still required. Strace shows that emerge isn't even looking for package.accept_keywords in the overlay. Reproducible: Always Steps to Reproduce: 1. Add '=category/package-version::repo ~arch' to '<overlay>/profiles/package.accept_keywords' 2. emerge -p =category/package-version::repo Actual Results: Emerge output indicates that a keyword change is still required. Expected Results: Emerge output should not indicate that a keyword change is still required.
For example, In my overlay, I wanted force =sys-apps/portage-2.1.11.57 to be installed on all my systems. I have the following files configured in my overlay/profiles folder: eapi: 5-progress. package.mask: <sys-apps/portage-2.1.11.57::gentoo package.accept_keywords: =sys-apps/portage-2.1.11.57::gentoo ~amd64 ~x86 I get the following from 'emerge -p =sys-apps/portage-2.1.11.57::gentoo': ---- The following keyword changes are necessary to proceed: (see "package.accept_keywords" in the portage(5) man page for more details) #required by =sys-apps/portage-2.1.11.57::gentoo (argument) =sys-apps/portage-2.1.11.57 ~amd64 ----
You can use package.keywords for this, see `man portage` and as an example /usr/portage/profiles/arch/amd64/x32/package.keywords.
I can't even get that far. Strace shows that emerge doesn't even bother looking for package.keywords or package.accept_keywords in the overlay. I suspect /usr/lib64/portage/pym/portage/package/ebuild/_config/KeywordsManager.py needs to be modified to look in each of the overlays for package.keywords or package.accept_keywords first, before any additional testing can be done.
These files are currently not supported. Refer to bug 370693 for other files that are support in ${repository}/profiles/.
I'd like to see this implemented as well.