1 |
On 11/13/2011 04:45 PM, Chí-Thanh Christopher Nguyễn wrote: |
2 |
> Zac Medico schrieb: |
3 |
>> On 11/13/2011 04:36 PM, Chí-Thanh Christopher Nguyễn wrote: |
4 |
>>> Zac Medico schrieb: |
5 |
>>>>> Per discussion on IRC, I propose to make -v turn off quiet-build by default. |
6 |
>>>>> It can remain enabled by default if -v is not passed to emerge. |
7 |
>>>> |
8 |
>>>> I think -v controls too many other things to make it override |
9 |
>>>> --quiet-build, especially since I consider --quiet-build=n to be a mode |
10 |
>>>> that most people would prefer to avoid. |
11 |
>>> |
12 |
>>> No, in my proposal --quiet-build would override -v, not the other way round. |
13 |
>> |
14 |
>> Your proposal was for -v to override the new default --quiet-build |
15 |
>> setting, was it not? |
16 |
> |
17 |
> To be more explicit: |
18 |
> 1) "emerge foo": quiet build |
19 |
> 2) "emerge foo --quiet-build=n": non-quiet build |
20 |
> 3) "emerge foo -v": non-quiet build |
21 |
> 4) "emerge foo -v --quiet-build=y": quiet-build |
22 |
> |
23 |
> So -v sets the default for quiet build, but user can still override with |
24 |
> explicit --quiet-build=... |
25 |
> |
26 |
> I think the case 1) covers the arguments in favour of having quiet build |
27 |
> by default. |
28 |
|
29 |
I think that's too fragile because you could easily have people using -v |
30 |
and getting the --quiet-build=n behavior even though they didn't want |
31 |
it. I think most people would prefer to avoid the --quiet-build=n |
32 |
behavior since, generally, people who want to analyze build output are |
33 |
better served by PORT_LOGDIR. |
34 |
-- |
35 |
Thanks, |
36 |
Zac |