Gentoo Archives: gentoo-dev

From: Zac Medico <zmedico@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] have portage be quiet by default
Date: Mon, 14 Nov 2011 15:06:31
Message-Id: 4EC12E48.9080502@gentoo.org
In Reply to: Re: [gentoo-dev] have portage be quiet by default by Dale
1 On 11/14/2011 05:11 AM, Dale wrote:
2 > Amadeusz Żołnowski wrote:
3 >> Excerpts from Dale's message of 2011-11-14 13:43:36 +0100:
4 >>> Amadeusz Żołnowski wrote:
5 >>>> Excerpts from Dale's message of 2011-11-14 13:17:28 +0100:
6 >>>>> Here is some feedback then. I liked it the way it was. When a
7 >>>>> build fails, I do a one of install of that package and I like to
8 >>>>> see the output. Why, because sometimes it gives me a hint as to
9 >>>>> why it failed or something I can google for.
10 >>>> If it fails you get tail of build.log, so you see it anyway.
11 >>> That doesn't always go back far enough tho. I have on my new rig seen
12 >>> the failure be as far back as a couple hundred lines.
13 >> Well, don't say that if problem is hundreds lines back you search it in
14 >> that output. I'd use for that purpose "less build.log" anyway.
15 >>
16 >>
17 >
18 > If emerge puts it on the screen like it always has, I won't need to go
19 > to any build.log. It will be there on the screen already since I have
20 > history set to save everything.
21
22 This is already the case with --quiet-build. In the event of a build
23 failure, emerge dumps the *entire* log to the terminal. So, the above
24 dialog is discussing a problem that doesn't even exist.
25 --
26 Thanks,
27 Zac