Bug #55321 - Add support for package.keywords in profiles. In profiles,

package.keywords modifies effective KEYWORDS values for a given ebuild. This
behavior is notably different from /etc/portage/package.keywords, which
instead modifies effective ACCEPT_KEYWORDS.

svn path=/main/trunk/; revision=12410

1 files changed, 21 insertions, 0 deletions

diff --git a/man/portage.5 b/man/portage.5
index 3e8eb7af..fac8c90e 100644
--- a/man/portage.5
+++ b/man/portage.5
@@ -29,6 +29,7 @@ eapi
 make.defaults
 packages
 packages.build
+package.keywords
 package.mask
 package.provided
 package.unmask
@@ -585,6 +586,26 @@ A list of all the packages which will be displayed when you run `emerge info`.
 .BR info_vars
 A list of all the variables which will be displayed when you run `emerge info`.
 .TP
+.BR package.keywords
+Per\-profile KEYWORDS. Useful for cases in which the effective KEYWORDS of a
+given package should vary depending on which profile the user has selected.
+
+.I Format:
+.nf
+\- comment lines begin with # (no inline comments)
+\- one DEPEND atom per line followed by additional KEYWORDS
+.fi
+
+.I Example:
+.nf
+# add stable keyword to libgd
+media\-libs/libgd x86
+# remove stable keyword from mplayer and add unstable keyword
+media\-video/mplayer \-x86 ~x86
+# remove all keywords from netcat
+net-analyzer/netcat -*
+.fi
+.TP
 .BR package.mask
 This contains a list of DEPEND atoms for packages that should not be installed 
 in any profile.  Useful for adding the latest KDE betas and making sure no