I'd like to be able to specify locally that I consider particular package versions to be "stable" even though the package maintainer hasn't marked it as stable yet. To do this, I'd like to be able to independently override the keywords for an ebuild. I've patched my copy of Portage (2.0.49-r19) to enable this capability with a simple hack. I will attach the patch. It causes Portage to look for a file called /etc/local_keywords. My copy of /etc/local_keywords currently contains only one line: sys-apps/baselayout-1.8.6.12-r3 x86 This means that I can continue to use "x86" as my ACCEPT_KEYWORDS, since I don't want to use ~x86 for most packages, and "emerge -u world" won't downgrade baselayout. (I'm trying out Linux 2.6, which seems to require the more recent version of baselayout.) Another way to achieve this would be to set package-specific ACCEPT_KEYWORDS lists. Instead of /etc/local_keywords, there might be a file called /etc/local_accept_keywords (or some shorter name) and I would put an entry in there that says I accept "~x86" for sys-apps/baselayout-1.8.6.12-r3 only. This might generalize better than my quick hack, since users could conceivably leave off the version number and accept "~x86" for any version of sys-apps/baselayout.
Created attachment 22978 [details, diff] Patch to enable local keyword overrides in Portage
*** This bug has been marked as a duplicate of 13616 ***
