On Sat, Apr 23, 2005 at 08:07:02AM -0400, Eric S. Johansson wrote:
> last time I checked, one could not do two or more emerges at the same
> time. Which raises the question would be OK to do an emerge fetch in
> one process and a straight emerge on the same set of files on a second?
> The rationale behind this is that if you can be fetching files prior
> to the time you need them, it might make the build process faster since
> you're now taking advantage of "parallel" operations.
>
> Of course, in order to do it correctly, there would need to be a per
> package lock in order to make sure that only one process was
> fetching/using the package at a time and to block package compilation
> when necessary.
>
> so, is as possible?
>
Is possible. With the caveats you mentioned.
Usually I don't pay much attention to the time savings. But the last
time I had to rebuild my system I found it extremely worth while to
run emerge -F <whatever> while glibc and gcc are compiling....
Without troubling too much over the exact logistics, I've sometimes
done
emerge -F --deep --update system
and run
emerge --update --deep system
while
emerge -F --deep --update world
runs on my laptop.
W
--
----------------------------------------------------------------
* Address: 45 Spelman Hall, Princeton University 08544 *
* Phone: x68958 AIM: AngularJerk *
* E-mail: [EMAIL PROTECTED] From: sep.dynalias.net *
----------------------------------------------------------------
From now on, I'll connect the dots my own way.
-- Calvin
Sortir en Pantoufles: up 12 days, 4:45
--
[email protected] mailing list
