From: realnc@arcor.de   
      
   J.O. Aho wrote:   
   > Nikos Chantziaras wrote:   
   >   
   >> According to eix, glibc-2.7-r2 is "~amd64".  Putting just   
   >> "sys-libs/glibc" in package.keywords (without ~* or **) unmasks it   
   >> correctly.  So that means every future glibc will be unmasked if it's   
   >> ~amd64?  (The same effect as putting "~amd64" in ACCEPT_KEYWORDS, but   
   >> only for glibc?)   
   >   
   > #Always use unstable version if there is one   
   > sys-libs/glibc ~amd64   
      
   What exactly happens if I omit "~amd64"?  (As I'm doing right now; I   
   have just "sys-libs/glibc".)   
      
      
   > Much depends on how you want to have things, but you should avoid using   
   >   
   > ACCEPT_KEYWORDS=~amd64 emerge something   
      
   I'm not doing that; I've read the heads-up warnings on gentoo-wiki.   
      
   One thing about ACCEPT_KEYWORDS though: should it be empty in make.conf?   
     I would have imagined that actually the default should have been   
   ACCEPT_KEYWORDS="amd64" :S   
      
      
   > If you want to use unstable, then better switch to unstable, see   
   > make.conf.example   
      
   Well, problem is that I don't know if I want to use unstable.  Right   
   now, I want to use stable but with one experimental package (GCC 4.3.0).   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)