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 1RPfK7-0000yS-Mq for garchives@archives.gentoo.org; Sun, 13 Nov 2011 19:02:42 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 78C2E21C04B; Sun, 13 Nov 2011 19:02:21 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 3AA9A21C03C for ; Sun, 13 Nov 2011 19:01:52 +0000 (UTC) Received: from [192.168.26.4] (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 AE3DE1B4013 for ; Sun, 13 Nov 2011 19:01:51 +0000 (UTC) Message-ID: <4EC0141E.2030900@gentoo.org> Date: Sun, 13 Nov 2011 11:01:50 -0800 From: Zac Medico User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:7.0.1) Gecko/20111102 Thunderbird/7.0.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: have portage be quiet by default References: <4EB4FA98.3080201@gentoo.org> <4EBD42EE.4060104@gentoo.org> <4EBEF208.5060500@gentoo.org> <201111121840.16686.vapier@gentoo.org> <4EBFBA75.3030500@gentoo.org> <1321188262-sup-4513@raeviah> In-Reply-To: X-Enigmail-Version: 1.4a1pre Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 84e8c692-9897-40fc-92b6-7b87fae38fca X-Archives-Hash: 0cfbf36cbac95f40322caa969e034d9c On 11/13/2011 08:24 AM, Duncan wrote: > The previous defaults made perfect sense to me already. Parallel emerge > jobs already puts portage in quiet mode, and that's what most people who > care (see my point above about whether this is the right distro choice or > not) should already be using. That default makes sense, since otherwise > the output would be jumbled anyway. > > 1-at-a-time merge defaults are therefore where the question is. Two > positions could be taken here. If it is argued that those who care will > already be using parallel mode in most cases, and that those who care but > that can't be bothered to switch their defaults really should be > questioning whether gentoo is an appropriate choice in the first place, > then a "noisy" default for 1-at-a-time makes sense too, because the only > time most (who care) will see it is when they're actually troubleshooting > something and thus deliberately using 1-at-a-time mode, in which case the > higher level of detail by default for that mode makes the the most sense. Ever since I added --jobs support, I've felt that suppression of build output would be a better default for at least the following reasons: 1) I estimate that the flooding of the terminal with build output is useless for more than 99% of users. Usually, there's too much information scrolling by at too high of a rate for it to be intelligible. Having this as the default behavior is ridiculous and leads to jokes like apt-gentoo [1]. Generally, people who want to analyze build output are best served by PORT_LOGDIR. 2) With --quiet-build, the user is presented with a useful summary of overall progress, along with current load average data. The output is consistent regardless of whether or not the emerge --jobs option is used. [1] http://chris-lamb.co.uk/2011/08/12/careful-what-you-wish-for/ -- Thanks, Zac