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 1RPy7C-0007Sd-Ps for garchives@archives.gentoo.org; Mon, 14 Nov 2011 15:06:31 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EDC0721C0EB; Mon, 14 Nov 2011 15:06:18 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 9AC7321C03E for ; Mon, 14 Nov 2011 15:05:45 +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 16D211B401C for ; Mon, 14 Nov 2011 15:05:45 +0000 (UTC) Message-ID: <4EC12E48.9080502@gentoo.org> Date: Mon, 14 Nov 2011 07:05:44 -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] 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> <4EBFCD5D.3080807@gentoo.org> <1321194595-sup-8983@raeviah> <4EBFE727.8000903@gentoo.org> <4EC02CC0.9080907@gentoo.org> <4EC04E11.3060500@gentoo.org> <4EC0559C.4020806@gentoo.org> <4EC106D8.9030402@gmail.com> <1321273331-sup-1733@ittemni> <4EC10CF8.2010904@gmail.com> <1321274837-sup-7585@ittemni> <4EC11398.7030200@gmail.com> In-Reply-To: <4EC11398.7030200@gmail.com> X-Enigmail-Version: 1.4a1pre Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: f061ed9d-9129-4c8e-b5aa-6ded23b3b32c X-Archives-Hash: bc7070299bd9711a10de8cc57eb9a5c6 On 11/14/2011 05:11 AM, Dale wrote: > Amadeusz =C5=BBo=C5=82nowski wrote: >> Excerpts from Dale's message of 2011-11-14 13:43:36 +0100: >>> Amadeusz =C5=BBo=C5=82nowski wrote: >>>> Excerpts from Dale's message of 2011-11-14 13:17:28 +0100: >>>>> Here is some feedback then. I liked it the way it was. When a >>>>> build fails, I do a one of install of that package and I like to >>>>> see the output. Why, because sometimes it gives me a hint as to >>>>> why it failed or something I can google for. >>>> If it fails you get tail of build.log, so you see it anyway. >>> That doesn't always go back far enough tho. I have on my new rig see= n >>> the failure be as far back as a couple hundred lines. >> Well, don't say that if problem is hundreds lines back you search it i= n >> that output. I'd use for that purpose "less build.log" anyway. >> >> >=20 > If emerge puts it on the screen like it always has, I won't need to go > to any build.log. It will be there on the screen already since I have > history set to save everything. This is already the case with --quiet-build. In the event of a build failure, emerge dumps the *entire* log to the terminal. So, the above dialog is discussing a problem that doesn't even exist. --=20 Thanks, Zac