Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux.gentoo    |    Stupid OS you gotta compile EVERYTHING    |    17,684 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 16,197 of 17,684    |
|    J.O. Aho to Nikos Chantziaras    |
|    Re: How can I emerge GCC 4.3.0?    |
|    03 Apr 08 18:46:19    |
      From: user@example.net              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              #Use unstable 2.7-r2 until a later version gets stable       =sys-libs/glibc-2.7-r2 ~amd64              Much depends on how you want to have things, but you should avoid using              ACCEPT_KEYWORDS=~amd64 emerge something              This will cause problems for you when you have to do something like       revdep-rebuild, as the system can't build the packages, and the same if you       use --deep when you emerge.              If you want to use unstable, then better switch to unstable, see       make.conf.example                     --               //Aho              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca