When /etc/make.profile points to a directory outside of /usr/portage/profiles, like /usr/local/portage/layman/mystuff/profiles/desktop, then package.keywords or package.unmask in that directory are ignored. However, the parent file is not. Reproducible: Always Steps to Reproduce: 1. Create a directory /usr/local/portage/layman/mystuff/profiles/desktop and symbolically link /etc/make.profile to it. 2. Put parent, package.keywords and package.unmask in there. 3. emerge <unmasked package> Actual Results: The contents of package.keywords and package.unmask are ignored when emerging. Expected Results: man 5 portage suggests that package.keywords and package.unmask put in /etc/make.profile/ would be read. It does say that site specific files should go into /etc/portage/profile/, but as a precaution because /usr/portage will be wiped on the next emerge --sync. The problem was hit when trying to manage a profile via an overlay. I had /usr/local/portage/layman/mystuff/profiles/desktop/parent contain /usr/portage/profiles/default/linux/x86/10.0/desktop and package.keywords contain sys-devel/automake ~x86 sys-devel/automake-wrapper ~x86 and package.unmask contain sys-devel/automake sys-devel/automake-wrapper Then emerge -uvpND world said nothing was to be updated. But when package.keywords and package.umasked were moved to /etc/portage, then I got [ebuild U ] sys-devel/automake-wrapper-4 [3-r1] 0 kB [ebuild U ] sys-apps/help2man-1.36.4-r1 [1.36.4] USE="nls" 84 kB [ebuild NS ] sys-devel/automake-1.11.1 [1.9.6-r2, 1.10.2] 0 kB
I am not using in-profile package.keywords correctly. Marking this bug as INVALID.
Oops, should give kudos to gengor :)
