* [gentoo-project] Council meeting: Tuesday 13 December 2011, 20:00 UTC
@ 2011-12-06 18:46 Fabian Groffen
2011-12-07 0:10 ` Zac Medico
0 siblings, 1 reply; 2+ messages in thread
From: Fabian Groffen @ 2011-12-06 18:46 UTC (permalink / raw
To: gentoo-project; +Cc: gentoo-dev-announce
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
The next council meeting will be at Tuesday 13 December 2011 at 20:00
UTC [1] in the #gentoo-council channel on Freenode.
Proposed agenda:
1. Intro / Roll call (5 minutes)
2. "Sighted pages" in the Gentoo wiki (5 minutes)
* Discuss/vote: Is this a council issue at the moment? [2]
If yes, schedule discussion 10-15 minutes before open floor.
3. Quiet build default in Portage (15 minutes)
* Discuss/vote: Should the quiet default get reverted before
affected Portage get stabilised? [3]
4. Open bugs with Council involvement (0 minutes)
* There are currently no open Council bugs
5. Open floor (10 minutes)
[1] http://www.gentoo.org/proj/en/council/utctolocal.html?time=2000
[2] http://archives.gentoo.org/gentoo-project/msg_01e478ad89a5a27ff42471ba37fba287.xml
[3] http://archives.gentoo.org/gentoo-project/msg_4e282bb4e6ac2611de2a39171a803c48.xml
--
Fabian Groffen
Gentoo on a different level
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [gentoo-project] Council meeting: Tuesday 13 December 2011, 20:00 UTC
2011-12-06 18:46 [gentoo-project] Council meeting: Tuesday 13 December 2011, 20:00 UTC Fabian Groffen
@ 2011-12-07 0:10 ` Zac Medico
0 siblings, 0 replies; 2+ messages in thread
From: Zac Medico @ 2011-12-07 0:10 UTC (permalink / raw
To: gentoo-project
[-- Attachment #1: Type: text/plain, Size: 354 bytes --]
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
[-- Attachment #2: 2011-12-20-emerge-quiet-build.en.txt --]
[-- Type: text/plain, Size: 1018 bytes --]
Title: emerge hides build output by default
Author: Zac Medico <zmedico@gentoo.org>
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-12-07 0:11 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-12-06 18:46 [gentoo-project] Council meeting: Tuesday 13 December 2011, 20:00 UTC Fabian Groffen
2011-12-07 0:10 ` Zac Medico
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox