Martin Vaeth wrote:
> J.O. Aho <user@example.net> wrote:
>> echo "=sys-devel/gcc-4.3.0 -* ~*" >> /etc/portage/package.keywords
>
> -* is obsolete, and using "=" is problematic since you wont get upgrades
> (which might be security relevant).
>
>> emerge =sys-devel/gcc-4.3.0
>
> The best way to unmask things is to use first "eix" or even "eix -l"
> for the package:
> It will show you whether ~ARCH (=nothing) is sufficient or whether you
> need * (or to specify the alien architecture directly) or ~* (or to
> specify the alien testing architecture directly) or even ** (to unmask
> regardless of anything).
> You should not use a stronger keywords than necessary to avoid undesired
> upgrades. eix -T (or eix-test-obsolete) will "warn" you if you used too
> much...

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?)

`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?