public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] question/feature request: First fetch, then compile...
Date: Wed, 17 Dec 2014 09:36:28 +0000	[thread overview]
Message-ID: <20141217093628.4762f5a2@digimed.co.uk> (raw)
In-Reply-To: <20141217065353.GC4439@solfire>

[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]

On Wed, 17 Dec 2014 07:53:53 +0100, meino.cramer@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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2014-12-17  9:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17  5:48 [gentoo-user] question/feature request: First fetch, then compile meino.cramer
2014-12-17  6:19 ` Dale
2014-12-17  6:27   ` meino.cramer
2014-12-17  6:34     ` Randolph Maaßen
2014-12-17  6:36     ` Dale
2014-12-17  6:41       ` Dale
2014-12-17  6:53         ` meino.cramer
2014-12-17  9:36           ` Neil Bothwick [this message]
2014-12-17  9:52             ` meino.cramer
2014-12-17 10:02               ` Dale
2014-12-17 12:13               ` Neil Bothwick
2014-12-17 13:58                 ` Matti Nykyri
2014-12-17 14:31                   ` meino.cramer
2014-12-17 15:25                     ` Poison BL.
2014-12-17  7:45 ` Helmut Jarausch
2014-12-17  8:22   ` Alan McKinnon
2014-12-17  8:41     ` meino.cramer
2014-12-17  8:42       ` Alan McKinnon
2014-12-17 18:24       ` Frank Steinmetzger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141217093628.4762f5a2@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox