1 |
Zac Medico schrieb: |
2 |
>> To be more explicit: |
3 |
>> 1) "emerge foo": quiet build |
4 |
>> 2) "emerge foo --quiet-build=n": non-quiet build |
5 |
>> 3) "emerge foo -v": non-quiet build |
6 |
>> 4) "emerge foo -v --quiet-build=y": quiet-build |
7 |
>> |
8 |
>> So -v sets the default for quiet build, but user can still override with |
9 |
>> explicit --quiet-build=... |
10 |
>> |
11 |
>> I think the case 1) covers the arguments in favour of having quiet build |
12 |
>> by default. |
13 |
> |
14 |
> I think that's too fragile because you could easily have people using -v |
15 |
> and getting the --quiet-build=n behavior even though they didn't want |
16 |
> it. I think most people would prefer to avoid the --quiet-build=n |
17 |
> behavior since, generally, people who want to analyze build output are |
18 |
> better served by PORT_LOGDIR. |
19 |
|
20 |
I think it is a solution which most of the critics of quiet-build could |
21 |
live with and users still won't see build output by default. |
22 |
|
23 |
If a user passes -v and as a result sees build output, I think he won't |
24 |
be confused or angry about it.[1] |
25 |
|
26 |
|
27 |
Best regards, |
28 |
Chí-Thanh Christopher Nguyễn |
29 |
|
30 |
[1] http://xkcd.com/242/ |