From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: --jobs
Date: Thu, 8 Dec 2011 07:50:47 +0700 [thread overview]
Message-ID: <CAA2qdGWJRTrKBx23dswPAdufJsXwfAtB_dbn7DZAw2FQvkZLVg@mail.gmail.com> (raw)
In-Reply-To: <87ehwf2abg.fsf@newsguy.com>
[-- Attachment #1: Type: text/plain, Size: 1834 bytes --]
On Dec 8, 2011 7:21 AM, "Harry Putnam" <reader@newsguy.com> wrote:
>
> Paul Hartman <paul.hartman+gentoo@gmail.com> writes:
>
> > On Wed, Dec 7, 2011 at 5:46 PM, Harry Putnam <reader@newsguy.com> wrote:
> >> This is a brand new install, and I've changed very little. I've done
> >> nothing consciously to effect how many jobs are to be run.
> >
> > In that case I think it is working normally. It won't run more than 1
> > job unless you ask it to do so.
>
> I followed another thread recently about this, and I understood the
> new behavior is set this way because emerge will be running more than
> 1 job and that would be a mess to put into one terminal... hence the
> line showing jobs.
>
> But if it is not default to run more than 1 job then why is the other
> (emerge) default in place, and blocking the normal output of -v?
>
-v affects only the list of packages being emerged, it no longer has any
effect on the build output.
> Seems like these defaults should all be on the same page.
>
> If emerge is not set to run more than 1 job at a time then the
> intrusive `--jobs ???? --load ????' baloney should not be in place by
> default either. But I'm sure our developers have much better reasons
> than I might dream up for doing it this (seemingly confusing) way.
>
It's not. The default is still "single job" and "no load limiting" but
"quietly build things"
> I'm not really complaining so much as just a little confused as to
> what is the reasoning for this change.
>
In the -project list, Zac explained his reasons. Some that I can recall:
* Computers are way too fast nowadays for us to properly peruse the build
output
* Gentoo newcomers are more likely to be confused by all those output. (And
my corollary: Gentoo oldtimers should be perfectly capable of finding out
how to disable quiet build ;-)
Rgds,
[-- Attachment #2: Type: text/html, Size: 2370 bytes --]
next prev parent reply other threads:[~2011-12-08 0:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 22:55 [gentoo-user] --jobs Harry Putnam
2011-12-07 23:08 ` Alan McKinnon
2011-12-07 23:46 ` [gentoo-user] --jobs Harry Putnam
2011-12-07 23:54 ` Paul Hartman
2011-12-08 0:09 ` Harry Putnam
2011-12-08 0:50 ` Pandu Poluan [this message]
2011-12-08 1:12 ` Neil Bothwick
2011-12-08 0:00 ` Neil Bothwick
2011-12-08 0:03 ` Claudio Roberto França Pereira
2011-12-08 0:05 ` Dale
2011-12-07 23:36 ` [gentoo-user] --jobs Paul Hartman
2011-12-08 0:13 ` [gentoo-user] --jobs Harry Putnam
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=CAA2qdGWJRTrKBx23dswPAdufJsXwfAtB_dbn7DZAw2FQvkZLVg@mail.gmail.com \
--to=pandu@poluan.info \
--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