-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Duncan wrote: > Beso <[EMAIL PROTECTED]> posted >>> Yes, I set ACCEPT_KEYWORDS=~amd64 (which automatically includes stable >>> amd64 as well, as shown by an emerge --info) in /etc/make.conf. You'd >>> be surprised at how far out of date stable arch is in some cases. Of >>> course in other cases, generally mature and real slow moving packages, >>> the latest version available has long been stable on most or all archs >>> (see below). >>> >> if i recall corectly in the past some packages that were under amd64 >> only needed also accept keywords amd64 near ~amd64. has this changed >> lately? usually the latest includes the former but sometimes when the >> packages are just amd64 and no ~amd64 ones i remember that i needed to >> add amd64 also in the keywords. > > I'm not saying it can't happen, but if it does, it's certainly a bug, > either of the package (not testing the keyword correctly) or of portage > (not setting it correctly), or possibly of the user (maybe a typo, ~adm64 > instead of ~amd64, say). > > Here's what I know: > > From my make.conf: > ACCEPT_KEYWORDS="~amd64" > > emerge --info |grep ACCEPT > ACCEPT_KEYWORDS="amd64 ~amd64" > > So portage is actively adding the amd64 stable keyword, based on the > ~amd64 in make.conf. It has done so since at least whatever portage was > around for 2004.1, which is when I started with Gentoo/~amd64. (As I > switched from Mandrake Cooker for AMD64, I never even seriously > considered stable Gentoo/amd64, and have run ~amd64 from day one.) As I > said, if it didn't work that way for some package, there was a bug > somewhere! > > Also note the wording in the handbook and the Code Listing 1.1 found here > (link should be a single line, in case I forget to come back and unwrap > this before sending or if it wraps on your end): > > http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml? > part=3&chap=3#doc_chap1 >
To clear up any misconceptions, setting ACCEPT_KEYWORDS is similar to setting USE - unless the magic keyword "-*" appears, portage will add the previous contents of ACCEPT_KEYWORDS to the value you set. As the amd64 keyword is already set in profiles/arch/amd64/make.defaults, the final setting ends up as "amd64 ~amd64". If you were to, for some reason set ACCEPT_KEYWORDS="~x86 ~amd64" in make.conf, the final value would be "amd64 ~amd64 ~x86" - which is not what you would want. (I, of course, strongly recommend NOT doing that, but that is what would result) - -- ABCD -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkksVrIACgkQOypDUo0oQOrtoQCgtjfsb8iORJxXSsPut3lqNAlr iggAoLYLHI55JcoWBC4zrNV1CDwKdF3G =Y8by -----END PGP SIGNATURE-----
