On 11/11/2011 07:11 AM, Mike Frysinger wrote: > On Thursday 10 November 2011 22:23:57 Zac Medico wrote: >> On 11/10/2011 07:17 PM, Zac Medico wrote: >>> On 11/10/2011 06:59 PM, Mike Frysinger wrote: >>>> On Thursday 10 November 2011 21:11:38 Zac Medico wrote: >>>>> On 11/10/2011 05:56 PM, Mike Frysinger wrote: >>>>>> On Thursday 10 November 2011 20:39:11 Mike Frysinger wrote: >>>>>>> if you want quiet portage output, use something like --quiet when >>>>>>> running emerge. the verbosity of the build output isn't really an >>>>>>> issue imo. >>>>>> >>>>>> perhaps a more controversial question: should we make --quiet the >>>>>> default >>>>> >>>>> I think --quiet-build would be a reasonable default, but --quiet >>>>> suppresses various warning messages that I think need to be enabled by >>>>> default for newbies. >>>> >>>> WFM >>>> >>>> would putting this as EMERGE_DEFAULT_OPTS in profiles/base/make.defaults >>>> be too hideous for people to swallow ? >>> >>> Less than sys-apps/portage-2.1.9.43 will choke on that, it's an >>> unrecognized option. So, we'd better just enable it by default for the >>> next portage release. >> >> Actually, it's been around since portage-2.1.7.5 (bug #291200). Still, >> it's probably better not to set it in the profile. > > 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 ? ;) > -mike
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=0cc174b6fc28feb26ea151d76f794e0ff2c2fa39 -- Thanks, Zac
