[gentoo-amd64] Re: gcc 4.1.0, emerge -e world

2006-06-24 Thread Duncan
Brian Litzinger [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Fri, 23 Jun 2006 16:47:21 -0700: I suppose there is a clever way to do this, but here is what I do: emerge -ep world foo Then I munge foo into a shell script with a bunch of individual emerge commands.

Re: [gentoo-amd64] Re: gcc 4.1.0, emerge -e world

2006-06-24 Thread Barry . SCHWARTZ
Duncan [EMAIL PROTECTED] skribis: emerge --resume works similarly, but if you stop the process and run a different emerge command, the different emerge command will erase the resume info so portage won't know where it left off... Another thing for the bag of tricks: Run emerge --resume,

Re: [gentoo-amd64] Re: gcc 4.1.0, emerge -e world

2006-06-24 Thread Michael Weyershäuser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: Duncan [EMAIL PROTECTED] skribis: emerge --resume works similarly, but if you stop the process and run a different emerge command, the different emerge command will erase the resume info so portage won't know where it

Re: [gentoo-amd64] Re: gcc 4.1.0, emerge -e world

2006-06-24 Thread Barry . SCHWARTZ
Michael Weyershäuser [EMAIL PROTECTED] skribis: [EMAIL PROTECTED] wrote: Run emerge --resume, suspend it, run the different emerge, then continue the emerge --resume. Even easier: 'emerge --ask --resume', leave it asking it's question, do your other emerge and then simply hit return on

Re: [gentoo-amd64] Re: gcc 4.1.0, emerge -e world

2006-06-24 Thread John Myers
On Saturday 24 June 2006 07:27, [EMAIL PROTECTED] wrote: Michael Weyershäuser [EMAIL PROTECTED] skribis: [EMAIL PROTECTED] wrote: Run emerge --resume, suspend it, run the different emerge, then continue the emerge --resume. Even easier: 'emerge --ask --resume', leave it asking it's