Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
On 12/06/2011 10:46 AM, Fabian Groffen wrote:
> 3. Quiet build default in Portage (15 minutes)
> * Discuss/vote: Should the quiet default get reverted before
> affected Portage get stabilised? [3]
For reference, I've attached a draft GLEP 42 news item for the new quiet
default. I plan to post this for review in a couple of weeks.
--
Thanks,
Zac
|
Title: emerge hides build output by default
Author: Zac Medico <zmedico@g.o>
Content-Type: text/plain
Posted: 2011-12-20
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: <sys-apps/portage-2.1.10.34
Beginning with sys-apps/portage-2.1.10.34, the emerge --quiet-build option is
enabled by default. This causes all build output to be hidden and redirected to
logs. If a build failure occurs, the entire build log automatically displayed.
Note that the default PORTAGE_ELOG_SYSTEM and PORTAGE_ELOG_CLASSES settings
cause elog messages to be displayed by emerge before it exits, regardless of
the --quiet-build setting. In order to have QA warning messages displayed,
developers should set PORTAGE_ELOG_CLASSES="${PORTAGE_ELOG_CLASSES} qa" in
make.conf, or use the developer profile which already contains this setting.
If you would like build output to be displayed by default, then set
EMERGE_DEFAULT_OPTS="--quiet-build=n" in make.conf. See the emerge(1) man page
for more information about this option.
|
|
