Mark Knecht wrote:
On Wed, Sep 14, 2011 at 4:46 PM, Neil Bothwick<[email protected]> wrote:
On Wed, 14 Sep 2011 15:37:15 -0700, Mark Knecht wrote:
3) Do the rest of the work
emerge -fDuN @world
emerge -pvDuN @world
Fix USE flag issues, if any
4) Do the build
emerge -DuN -j13 @world
There's not point in doing the fetch first, portage has done parallel
fetching for some time - it's faster to let the distfiles download while
the first package is compiling.
emerge -auDN @world covers all of that - except the -j which is
system-dependent.
--
Neil Bothwick
Quite true about the parallel fetch, but I still do this anyway
because I want to know all the code is local before I start. With 12
processor cores I often build the first file before the second has
been downloaded. Also I don't want to start a big build, say 50-70
updates, and then find out an hour later when I come back that some
portage mirror choked on finding a specific file and the whole thing
died 10 minutes in. This way I have a better chance of getting to the
end in one pass.
Anyway, it works well for this old dog, and in my mind there is a good
reason to fetch before building but I can see how others might not
want to do that.
- Mark
tail -f /var/log/emerge-fetch.log
That way you can be compiling and watching the fetching process at the
same time. If something fails, it'll be printer there. I use it all
the time here. I only have 4 cores here tho. :-P
Dale
:-) :-)
