On 11/09/06, Tomek Lutelmowski <[EMAIL PROTECTED]> wrote:
On Mon, 11 Sep 2006 21:59:44 +0100, Kerin Millar wrote
> The standard amd64 hardened profile isn't multilib enabled anyway
> (whereas hardened/amd64/multilib is). I agree with Mike, you'd be
> better of doing it the "right way" and using the correct profile.
> That's what they're there for :)
I see, unfortunately this "hardened" profile has old glibc and gcc packages.
Of course I cant revert to old version of glibc in my system :-(
Ah, that's true - glibc-2.4 (and gcc-4 for that matter) is vetoed in
the hardened profile (see
/usr/portage/profiles/hardened/package.mask). Given that you're
already using the newer version of glibc, you could simply try
overriding this policy and unmasking it:
echo "=sys-libs/glibc-2.4*" >> /etc/portage/package.unmask
The alternative approach would be to prevent the profile you are using
now from masking the hardened USE flag which, if memory serves
correctly would be accomplished as follows:
echo "-hardened" >> /etc/portage/profile/use.mask
I would still recommend adapting the hardened profile to your needs
rather than vice versa.
Cheers,
--Kerin
--
[email protected] mailing list
