From: vaeth@mathematik.uni-wuerzburg.de   
      
   Nikos Chantziaras  wrote:   
   > J.O. Aho wrote:   
   >>   
   >> #Always use unstable version if there is one   
   >> sys-libs/glibc ~amd64   
   >   
   > What exactly happens if I omit "~amd64"?   
      
   Nothing, this is equivalent: An empty entry is a shortcut for ~ARCH.   
      
   > 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   
      
   Also here, it doesn't matter: The default is ACCEPT_KEYWORDS="$ARCH"   
   and everything which you add in make.conf is just added   
   (with the exception of "-*" which - in the new syntax - clears everything   
   which was in this string before).   
      
   >> 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.   
      
   Probably, there is not *so* much difference in the stability which   
   you will actually observe. However, the main difference is the number   
   of packages which you will have to recompile: There are much more often   
   new ~ARCH versions than new ARCH versions (especially for amd64).   
   And stepping back can be difficult. For example, downgrading glibc usually   
   breaks your system (current ebuilds even won't allow it at all).   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)