On Wed, 17 Dec 2014 10:52:44 +0100, meino.cra...@gmx.de wrote: > > > 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.
> 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? pgrep wget will tell you if a download is still in progress. It seems reasonable to assume that if there is no further output to the log and wget is no longer running, portage is no longer downloading files. Or you could get clever and set FETCH_COMMAND to a script that fetches the file and then notifies of completion. > How can the script check for "the last needed file has been downloaded > successfully" ? It can't, any more than portage does. Whether the download phases exists successfully or unsuccessfully your Internet connection is no longer being used, so you may as well shut down the PC. You are trying to use portage in a way that was not intended. That involves compromises, some work or both. Another alternative would be to use a USB to ethernet adaptor on the embedded board and connect it directory to your router. -- Neil Bothwick The word 'Windows' is a word out of an old dialect of the Apaches. It means: 'White man staring through glass-screen onto an hourglass...')
pgpJiiv0J62Xk.pgp
Description: OpenPGP digital signature
