Gentoo Archives: gentoo-dev

From: Dale <rdalek1967@×××××.com>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: have portage be quiet by default
Date: Mon, 14 Nov 2011 12:37:28
Message-Id: 4EC10B5D.3070204@gmail.com
In Reply to: Re: [gentoo-dev] Re: have portage be quiet by default by Zac Medico
1 Zac Medico wrote:
2 > On 11/13/2011 08:24 AM, Duncan wrote:
3 >> The previous defaults made perfect sense to me already. Parallel emerge
4 >> jobs already puts portage in quiet mode, and that's what most people who
5 >> care (see my point above about whether this is the right distro choice or
6 >> not) should already be using. That default makes sense, since otherwise
7 >> the output would be jumbled anyway.
8 >>
9 >> 1-at-a-time merge defaults are therefore where the question is. Two
10 >> positions could be taken here. If it is argued that those who care will
11 >> already be using parallel mode in most cases, and that those who care but
12 >> that can't be bothered to switch their defaults really should be
13 >> questioning whether gentoo is an appropriate choice in the first place,
14 >> then a "noisy" default for 1-at-a-time makes sense too, because the only
15 >> time most (who care) will see it is when they're actually troubleshooting
16 >> something and thus deliberately using 1-at-a-time mode, in which case the
17 >> higher level of detail by default for that mode makes the the most sense.
18 > Ever since I added --jobs support, I've felt that suppression of build
19 > output would be a better default for at least the following reasons:
20 >
21 > 1) I estimate that the flooding of the terminal with build output is
22 > useless for more than 99% of users. Usually, there's too much
23 > information scrolling by at too high of a rate for it to be
24 > intelligible. Having this as the default behavior is ridiculous and
25 > leads to jokes like apt-gentoo [1]. Generally, people who want to
26 > analyze build output are best served by PORT_LOGDIR.
27
28 One key. Scroll Lock. You can look all you want then hit it again to
29 let it carry on. There is also ctrl Z as well. I use that a good bit
30 to see what is going on. Just type in fg to carry on.
31
32 As for progress, genlop -c does that already.
33 >
34 > 2) With --quiet-build, the user is presented with a useful summary of
35 > overall progress, along with current load average data. The output is
36 > consistent regardless of whether or not the emerge --jobs option is used.
37 >
38 > [1] http://chris-lamb.co.uk/2011/08/12/careful-what-you-wish-for/
39
40 Unless you are trying to compile one that failed earlier. Then you
41 don't want the default, you want to see what made it fail. Then google
42 is our friend again.
43
44 That said, GREAT work on portage. :-D
45
46 Dale
47
48 :-) :-)

Replies

Subject Author
Re: [gentoo-dev] Re: have portage be quiet by default Zac Medico <zmedico@g.o>