meino.cra...@gmx.de wrote: > Neil Bothwick <n...@digimed.co.uk> [14-12-17 10:40]: >> On Wed, 17 Dec 2014 07:53:53 +0100, meino.cra...@gmx.de wrote: >> >>>>> 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. >>>> 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? >>> Yes, thats it: First download all stuff THEN start compiling. >> Why? The downloads will happen at the same rate but you'll have a head >> start on the compiling. The only disadvantage i can see is that you will >> not have a notification of when the download finishes, but you could work >> around that by having another script check emerge-fetch.log and send a >> shutdown to the PC when there is no further output. >>> Would --jobs=0 help here? This would say "No packages are build >>> simultanously"...I check that! >> No. --jobs controls package building, nothing to do with downloading. >> parallel-fetch in the closest to what you want as it grabs all the >> downloads as soon as possible. >> >> >> -- >> Neil Bothwick >> >> And on the seventh day God said :wq and then make > Hi Neil, > > how can I (or the script) distinguish between an internet > connection, which is heavily slowed down (no data), blocked or an currently > not responding server and the end of all needed downloads? > > How can the script check for "the last needed file has been downloaded > successfully" ? > > Best regards, > Meino > >
If I understand you correctly, emerge can run into the same issue. If for example it needs to download a tarball or patch and the server that has it is not available, then emerge will skip that, download the rest and then stop fetching. So, either way, you can end up with things not downloaded. At least with the fetch option, it does all this at the beginning of the process instead of when it gets to the package it wants to emerge. The only way I see for this to work and not have to compute twice, set the fetch option, start the emerge and then monitor the fetch log. When it is done with the fetch part, then you can disconnect the internet connection and it should continue compiling. Other than that, I don't know of a way to do what you want. It is 4AM here so that may cloud up things a bit here. :/ Dale :-) :-)
