On 12 November 2011 15:40, Mike Frysinger <vap...@gentoo.org> wrote: > On Saturday 12 November 2011 17:24:08 Patrick Lauer wrote: >> On 11/11/11 16:44, Zac Medico wrote: >> >> good point. we don't want to punish old portage users. let's enable it >> >> by default in portage itself then. just add `elog` output to the >> >> portage ebuild to inform users of the change ? or do we want a news >> >> item ? >> >> >> >> what's the flag to negate the default ? --no-quiet-build ? ;) >> > >> > It's --quiet-build=n. I've gone ahead and enabled it for release in >> > portage-2.1.10.34: >> > >> > http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=0cc1 >> > 74b6fc28feb26ea151d76f794e0ff2c2fa39 >> >> Lots of people in #gentoo are unhappy with it. > > most changes people will be unhappy with because it's different
I'm a bit surprised by the negative comments. I was pleasantly surprised this morning when I discovered the clean output now generated by default by Portage. After all, most of the time the build logs are "useless". By that I mean that one only looks at them when the build fails. So not seeing them by default seems the right thing to do. This may not always be true (especially for devs) but changing the default is very simple in those special cases. By the way, is there a noticeable difference in build time (for relatively large builds) when logging to the console is off? Not important, just curious. >> Most devs will be unhappy as it makes it harder to view the log while >> building. > > devs are not the normal case. it's trivial to have them use --quiet-build=n > in their default emerge opts. > -mike
