Probably make.conf is the only place that really even mentions them. But
basically, in an ebuild is a list of KEYWORDS. Currently I believe the only
use of KEYWORDS is to define what architectures (sparc, x86, ppc, ...) a
package works on. In your make.profile, make.defaults sets ACCEPT_KEYWORDS
to x86, because you're almost certainly using default-x86-1.4. You're using
default-x86-1.4 because that's what your stage tarball came with; you used
to have to set the link manually but that was back in the 1.0 days.
Anyway, for every arch keyword there's a corresponding ~arch keyword, which
indicates that the package is works-for-me stable (me being the developer)
and ready for testing by general users.
Portage ties all of this together by comparing your ACCEPT_KEYWORDS to the
ebuild's KEYWORDS, and if there aren't any shared, it considers the package
masked. So an ebuild is first put into the portage tree with KEYWORDS="~x86"
and only people with ~x86 see it unmasked; later, the ebuild is marked
stable with KEYWORDS="x86". Note that like many other variables in
make.{globals,defaults,conf}, ACCEPT_KEYWORDS is cumulative, so even if you
set ACCEPT_KEYWORDS="~x86" in make.conf, you still have x86 too.Or maybe you're asking why it's x86, in which case: 8086, 286, 386, 486, 586 (pentium), 686 (pentium 2+)...x86...get it? -Heschi > What document explains the use of these key words? I really need to go > read it and understand. -- [EMAIL PROTECTED] mailing list
