Re: [gentoo-user] Nasty bugs in portage?

[Frank Schafer <frank.schafer@t-systems.cz>]

On Mon, 2005-09-12 at 08:33 +0100, Neil Bothwick wrote:
> > If I get it right ``fix_libtool_files.sh'' corrects the settings for
> > libtool according to the native compiler if gcc has changed. During a
> > native install there isn't an older version of gcc. So this should be
> > (and was) the wrong answer.
> 
> Fair comment, but emerge --resume is still important. your original post
> seemed to assume that after fixing the problem, you'd have to run emerge
> --emptytree again, which is not the case. It is annoying to have to stop
> the process to fix something, but not so nearly annoying as if you have
> to start over.
> 
> 
That's very right and we should be glad to have this switch :)

I did a lot of experiments on saturday and yesterday. So I decided to
make the whole procedure (starting with making the filesystems) what
took about 10 minutes and then:

``scripts/nootstrap.sh && touch /var/log/portage/bootstrap && emerge
--oneshot --nodeps autoconf && emerge --oneshot --nodeps
autoconf-wrapper && emerge --oneshot --nodeps python &&
touch /var/log/portage/bugworkaround && emerge --emptytree system''

After firing up this command I went to sleep. If the comp works hard
meanwhile I'm having sweet dreams about my pets ... this don't hurt so
much ;)

In the morning the system was up and ``ls -ltr /var/log/portage'' showed
me that it took something about 5 hours.

Thanks for your assistence
Frank

-- 
gentoo-user@gentoo.org mailing list