public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: meino.cramer@gmx.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] question/feature request: First fetch, then compile...
Date: Wed, 17 Dec 2014 07:53:53 +0100	[thread overview]
Message-ID: <20141217065353.GC4439@solfire> (raw)
In-Reply-To: <5491258F.2080406@gmail.com>

Dale <rdalek1967@gmail.com> [14-12-17 07:44]:
> Dale wrote:
> > meino.cramer@gmx.de 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
> 
> :-)  :-) 
> 

Hi Dale,

thanks for your reply!
thanks for your reply!
thanks for your reply!
thanks for your reply!

You are posting faster, than I am able to answer... :)

I am no native english speaker...sorry if I wrote confusing
things.

Yes, thats it: First download all stuff THEN start compiling.

Would --jobs=0 help here? This would say "No packages are build
simultanously"...I check that!

Best regards,
Meino






  reply	other threads:[~2014-12-17  6:54 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 [this message]
2014-12-17  9:36           ` Neil Bothwick
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=20141217065353.GC4439@solfire \
    --to=meino.cramer@gmx.de \
    --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