From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RXGZr-0004Lx-Lu for garchives@archives.gentoo.org; Sun, 04 Dec 2011 18:14:15 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5E71221C194; Sun, 4 Dec 2011 18:14:02 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 8CDDF21C193 for ; Sun, 4 Dec 2011 18:13:49 +0000 (UTC) Received: from [192.168.26.2] (ip98-164-193-252.oc.oc.cox.net [98.164.193.252]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: zmedico) by smtp.gentoo.org (Postfix) with ESMTPSA id 0155F1B4013 for ; Sun, 4 Dec 2011 18:13:48 +0000 (UTC) Message-ID: <4EDBB85B.7060203@gentoo.org> Date: Sun, 04 Dec 2011 10:13:47 -0800 From: Zac Medico User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111120 Thunderbird/8.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org MIME-Version: 1.0 To: gentoo-project@lists.gentoo.org Subject: Re: [gentoo-project] Re: [gentoo-dev-announce] Call for agenda items -- Council meeting 2011-12-13 References: <20111203103024.GN37825@gentoo.org> <4EDB80F8.1090800@gentoo.org> In-Reply-To: <4EDB80F8.1090800@gentoo.org> X-Enigmail-Version: 1.3.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: a79cfc88-242d-4a46-8372-e95e1fc00b9a X-Archives-Hash: 91d86bafde17975b1a02fe9431d759a2 On Sun, Dec 4, 2011 at 6:17 AM, Thomas Sachau wrote: > 2. Should the default output of portage be changed to quiet? > > If yes, is a simple portage message for 2.1.* users enough to inform > users about this highly visible change? Especially in the context in > mind, that a good amount of packages have elog messages, so it is pretty > easy to miss this hint for a change in portage behaviour. I'm already planning to send out a GLEP 42 news item for this before it goes to stable. It will include a description of --quiet-build behavior (including automatic display of build output when a build fails), how to use EMERGE_DEFAULT_OPTS to customize the local default, and how the default PORTAGE_ELOG_SYSTEM/PORTAGE_ELOG_CLASSES settings ensure that elog messages are displayed regardless of the --quiet-build setting. -- Thanks, Zac