View Single Post

   
  #2 (permalink)  
Old 04-07-2008, 08:36 AM
Martin Vaeth
 
Posts: n/a
Default Re: How can I emerge GCC 4.3.0?

Nikos Chantziaras <realnc@arcor.de> wrote:
>
> 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?)


Exactly (supposed your ARCH is amd64). This is usually what you want,
because security issues are usually not fixed (and sometimes not even
reported) for ~ARCH versions, i.e. *if* you run an ~ARCH version, better
use the highest one.

> `eix -l gcc` says that 4.3.0 is "**". So I guess ">=sys-libs/gcc-4.3.0
> **" is the correct way to unmask until GCC 4.3 enters ~amd64?


Yes. And when this happens, you should remove the "**" unless you want
to continue to install the newest bleeding edge gcc. (This is why
eix-test-obsolete informs about it - of course, only if you run it
after eix-sync and *before* emerge -NDu world).
Reply With Quote