Re: How can I emerge GCC 4.3.0? 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 |