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
signature.asc
Description: PGP signature
