From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: --jobs
Date: Thu, 8 Dec 2011 01:12:31 +0000 [thread overview]
Message-ID: <20111208011231.7079934e@digimed.co.uk> (raw)
In-Reply-To: <87ehwf2abg.fsf@newsguy.com>
[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]
On Wed, 07 Dec 2011 18:09:39 -0600, Harry Putnam wrote:
> 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.
No, the compile output has been hidden for --jobs >1 for a long time.
The new quiet-build behaviour applies the same output rules when --jobs
is not in effect.
> 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?
This was also covered in the other thread. The new default does not hide
the verbose output of emerge (the command to which -v is applied) it
hides the autotools and compiler output, which generally does nothing but
hide the useful information amongst tens of megabytes of
blurred, rapidly scrolling, uninformative text.
That you have to explicitly enable this output is consistent with also
having to enable verbose output on emerge and most other programs.
--
Neil Bothwick
"Facts are stubborn things, but statistics are more pliable."
- Mark Twain
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-12-08 1:14 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
2011-12-08 1:12 ` Neil Bothwick [this message]
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=20111208011231.7079934e@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