Re: [gentoo-user] USE one more time!

[brett holcomb]

Thank you, Matt, for the explanation. That clears it up. My PIII dual 933 is on glibc after 10 hours so maybe sometime this week it will finish!

On Fri, 21 Feb 2003 06:13:23 -0800
Matt Tucker <[EMAIL PROTECTED]> wrote:

-- Jonathan Chocron <[EMAIL PROTECTED]> spake thusly:

I have noticed the same thing, it is due to the export
CONFIG_PROTECT="-*" instruction that you pass right
before emerging portage. I only see one solution : you can 'export CONFIG_PROTECT_MASK="/etc/make.conf"'

Hope this helps

Actually, trying to set CONFIG_PROTECT_MASK="/etc/make.conf" won't
work, for a couple reasons. First of all, protect_mask means "don't
protect". It's for marking directories under CONFIG_PROTECT which
shouldn't be protected. What would make more sense is
CONFIG_PROTECT="-* /etc/make.conf", but this won't work either, because
the config_protect mechanism only deals with directories. Trying to set
it to /etc/make.conf will simply ensure that any files that want to
install to /etc/make.conf/... are protected. And there obviously aren't
any.

In regards to bootstrap.sh, it copies make.conf before starting, and
then restores it when complete. This is good because it also explicitly
does CONFIG_PROTECT="-*" and then immediately "emerge portage", which
overwrites the make.conf you've just so carefully created. But if you
look more closely, it actually is doing this:

read make.conf settings into environment (including CFLAGS)
backup make.conf
emerge portage (overwrites make.conf)
emerge baselayout texinfo gettext binutils gcc
emerge glibc baselayout texinfo gettext zlib binutils gcc
restore make.conf

So everything gets built optimized during bootstrap, but it's not
obvious from the filesystem.

--
[EMAIL PROTECTED] mailing list