Presently many ebuilds use the form: use blah && do something This spits out "blah" while the ebuild is building... This is hardly a serious bug but it's some screen garbage. In fact I wouldn't care but it CAN be fixed without breaking the other form: if [ "`use blah`" ]; then Here is a new use() function which makes "use" quiet when outputting to stdout, so both forms above continue to work. use() { local x for x in ${USE} do if [ "${x}" = "${1}" ] then tty --quiet </dev/stdout || echo "${x}" return 0 fi done return 1 } Reproducible: Always Steps to Reproduce: 1. emerge xmms (I'm sure there are better examples) 2. watch the output as the emerge starts Actual Results: # emerge xmms Calculating dependencies ...done! >>> emerge (1 of 1) media-sound/xmms-1.2.7-r19 to / >>> md5 ;-) xmms-1.2.7.tar.gz >>> md5 ;-) xmms-1.2.7-mmx.patch.gz >>> Unpacking source... >>> Unpacking xmms-1.2.7.tar.gz to /var/tmp/portage/xmms-1.2.7-r19/work * Applying xmms-jump.patch... [ ok ] * Applying xmms-sigterm.patch... [ ok ] x86 mmx * Applying xmms-1.2.7-mmx.patch.gz... [ ok ] Expected Results: # emerge xmms Calculating dependencies ...done! >>> emerge (1 of 1) media-sound/xmms-1.2.7-r19 to / >>> md5 ;-) xmms-1.2.7.tar.gz >>> md5 ;-) xmms-1.2.7-mmx.patch.gz >>> Unpacking source... >>> Unpacking xmms-1.2.7.tar.gz to /var/tmp/portage/xmms-1.2.7-r19/work * Applying xmms-jump.patch... [ ok ] * Applying xmms-sigterm.patch... [ ok ] * Applying xmms-1.2.7-mmx.patch.gz... [ ok ]
Nice... I'll have to think about whether or not to add it... I've got it in there, but commented out. The extra output is informational, and I kinda like it.
FWIW, I'd prefer quieter ebuilds (unless emerge --verbose is used).
Looks to me like this was applied at some point so I'm closing this bug.
