The PORTAGE_QUIET variable that gets set when running emerge -q should affect the econf and emake functions, or there should be other options (--quiet-econf/--quiet-emake) that emerge could use. I added these lines to the econf() function in /usr/lib/portage/bin/ebuild.sh: if [ ${PORTAGE_QUIET} -eq 1 ]; then LOCAL_EXTRA_ECONF="--quiet ${LOCAL_EXTRA_ECONF}" fi And I did the same in /usr/lib/portage/bin/emake: if [ ${PORTAGE_QUIET} -eq 1 ]; then EXTRA_EMAKE="--quiet ${EXTRA_EMAKE}" fi But this also makes portage suppress ">>> Configuring" and ">>> Compiling" which would be nice to see.
I'm unsure about how I feel about doing this by default when the -q option is invoked. portage internally does however use a noise level. Perhaps if the -q option was invoked more than one time then --quiet could be propagated into emake,econf
I think we can close this, since we have --quiet-build now. We the option, all output goes to logs only. Is there any other reason to want something like that?
We do have a few other PORTAGE_QUIET conditionals spread through portage's bash code. I tend to agree that it's practically irrelevant since emerge -q sends output to logs now. However, the PORTAGE_QUIET conditionals may still be useful for people using the ebuild(1) command for development.
PORTAGE_QUIET is used by /etc/portage/postsync.d/q-reinitialize: #!/bin/sh [ -x /usr/bin/q ] && /usr/bin/q -r ${PORTAGE_QUIET:+-q} : It allows me to have a completely quiet emerge --sync for instance. So I think this bug can be closed, as --quiet-build is here and PORTAGE_QUIET is still useful.
