On Dec 8, 2011 7:21 AM, "Harry Putnam" <rea...@newsguy.com> wrote: > > Paul Hartman <paul.hartman+gen...@gmail.com> writes: > > > On Wed, Dec 7, 2011 at 5:46 PM, Harry Putnam <rea...@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,
