From: pk@pk.invalid   
      
   Nikos Chantziaras wrote:   
      
   >> #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".)   
      
   Man portage says that "lines without any KEYWORDS imply unstable host arch".   
   However, I always prefer to explicitly specify the arch keyword (eg,   
   ~amd64).   
      
   > 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   
      
   It should be either unset or nonempty (I don't know what happens it you   
   explicitly set it to the empty string; might work and assume stable, but   
   I'm not sure).   
   Take a look at /etc/make.conf.example (don't know if you have it; with   
   normal text-mode install it's there). Basically, each value that is not   
   explicitly set in make.conf has a default value. The file make.conf.example   
   does a good job at showing what these defaults are (I usually take that   
   file as a starting point for a new install, instead of the almost empty   
   make.conf provided).   
   A way to see your current configuration (and thus see defaults for values   
   you have not set) is to run "emerge --info" or to use the portageq tool   
   (portageq --help for help)   
      
   > 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).   
      
   If you want to use unstable, just be prepared to upgrade packages frequently   
   and encounter some occasional breakage. And, of course, with an unstable   
   system it's almost mandatory to run emerge --sync and emerge world quite   
   often.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)