ACCEPT KEYWORDS/zh

Article description::The ACCEPT_KEYWORDS variable informs the package manager which ebuilds' [[KEYWORDS values it is allowed to accept.]]

Where the variable is set?
The variable is usually set through the Gentoo profile but can be overruled system wide in, per-package in , or even for a single emerge on the command line, though this is not recommended.

Stable and unstable keywords
The default value of most profiles' ACCEPT_KEYWORDS variable is the architecture itself, like  or. In these cases, the package manager will only accept ebuilds whose KEYWORDS variable contains this architecture. If the user wants to be able to install and work with ebuilds that are not considered production-ready yet, they can add the same architecture but with the  prefix to it, like so:

One should not specify the stable keyword when adding the testing keyword  because ACCEPT_KEYWORDS is an incremental variable.

If the setting is not to be made system-wide, then it can be set per-package in the file or directory:

In addition to the normal values from ACCEPT_KEYWORDS, supports three special tokens :


 * — Package is visible if it is stable on any architecture.
 * — Package is visible if it is in testing on any architecture.
 * — Package is always visible ( KEYWORDS are ignored completely).

The last choice is useful for live package versions (e.g. SVN/Git/Mercurial package versions) because live ebuilds don't have a KEYWORDS variable.