From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.50) id 1ESG0E-0004sN-Gb for garchives@archives.gentoo.org; Wed, 19 Oct 2005 15:37:18 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id j9JFWUZj009720; Wed, 19 Oct 2005 15:32:30 GMT Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id j9JFWUnU028994 for ; Wed, 19 Oct 2005 15:32:30 GMT Received: from list by ciao.gmane.org with local (Exim 4.43) id 1ESFvV-0002gZ-SH for gentoo-amd64@lists.gentoo.org; Wed, 19 Oct 2005 17:32:25 +0200 Received: from ip68-230-97-182.ph.ph.cox.net ([68.230.97.182]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 19 Oct 2005 17:32:25 +0200 Received: from 1i5t5.duncan by ip68-230-97-182.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 19 Oct 2005 17:32:25 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-amd64@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-amd64] Re: Re: Upgrading from amd64 to ~amd64. Date: Wed, 19 Oct 2005 08:25:14 -0700 Organization: Sometimes Message-ID: References: <030001c5d38e$c93d1f10$0203a8c0@oulaptop> <33411.202.248.61.99.1129607716.squirrel@gw.thefreemanclan.net> <43551B8D.7070108@cs.ubishops.ca> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: ip68-230-97-182.ph.ph.cox.net User-Agent: Pan/0.14.2.91 (As She Crawled Across the Table) Sender: news X-Archives-Salt: a95a2f35-10a6-4eff-9f15-cd9ec2f558f9 X-Archives-Hash: 9288b8325a976531e3b5e8a685f382f1 Scott Stoddard posted <43551B8D.7070108@cs.ubishops.ca>, excerpted below, on Tue, 18 Oct 2005 11:58:05 -0400: > Duncan wrote: >> changed USE flags vs what you currently have merged.) After each level >> below, I run etc-update, so the number of pending updates doesn't get out >> of hand. Of course, if the current version of any package later in the > > Of course, during those big emerge jobs, you can opt to run etc-update > in another terminal while the emerge is still progressing. I tend to > use this option to save time sorting through the lists while my machine > _isn't_ doing something more productive. /Very/ good point! Me too! In fact, with a dual Opteron, one of the things I do with emerge -p is use the --tree switch as well, to see which emerges depend on each other, then run two or three independent emerge sessions at once, to make full use of the CPUs, while running etc-updates and emerge --pretend --changelog and other such stuff in a forth session. Yes, portage has the jobs thing, but many emerges don't do parallel jobs all that efficiently, or turn them off because it screws up the compile dependency order for certain packages. Checking for dependencies then doing independent emerge sessions where no dependencies exist overcomes that issue. Of course, that only works once one gets past the critical toolchain steps. If you want everything else compiled with the newest gcc, you can't run parallel emerges until gcc itself is merged. However, one can still run etc-update and the like in parallel, even where parallel emerges aren't possible. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- gentoo-amd64@gentoo.org mailing list