Dale wrote: > [email protected] wrote: > >> Hi Dale, >> >> thanks for your reply ! :) >> >> I know of that flag, but it does not exaclty what I want. >> It parallelizes compilation and downloading. >> >> How can I exactly determine, that the last file has been >> downloaded without watching the monitor all the (because >> these are embedded systems: "long") time? >> >> Best regards, >> Meino >> >> > Note that says parallel-fetch not build. From the man page: > > parallel-fetch: Fetch in the background while compiling. Run `tail -f > /var/log/emerge-fetch.log` in a terminal to view parallel-fetch progress. > > What you are thinking about is --jobs, or -j. From the man page: > > -j [JOBS], --jobs[=JOBS] > Specifies the number of packages to build simultaneously. If this option > is given without an argument, emerge will not limit the number of jobs > that can run simultaneously. Also see the related --load-average option. > Similarly to the --quiet-build option, the --jobs option causes all > build output to be redirected to logs. Note that interactive packages > currently force a setting of --jobs=1. This issue can be temporarily > avoided by specifying --accept-properties=-interactive. > > The setting of parallel-fetch should do exactly what you want done. > > Dale > > :-) :-) >
Ahh, I think I see what you are saying. You want it to fetch and NOT compile until the fetch is finished. I'm not sure if there is a way to do that or not. Since it should be able to compile and fetch at the same time, why not try it that way and see how well it works? Dale :-) :-)
