| 1 |
Zac Medico schrieb: |
| 2 |
> On 11/13/2011 07:49 AM, Thomas Sachau wrote: |
| 3 |
>> Please give me a good reason, why i should by default do more things (adding quiet-build=n to the |
| 4 |
>> default emerge opts or searching for and opening the build.log) and what i or others do get from |
| 5 |
>> that. And less lines on the screen is no added value for me, it removes value. |
| 6 |
> |
| 7 |
> Why should we expose new users to legacy defaults that are useless to |
| 8 |
> more than 99% users, when they would most likely prefer the |
| 9 |
> --quiet-build display? |
| 10 |
|
| 11 |
Why should we change the default behaviour for existing users? Those, who dont want to see it, |
| 12 |
probably already use --jobs or quiet-build=y. For the rest, they either dont know about those |
| 13 |
options (which does not get better, if some default behaviour changes) or they dont want those |
| 14 |
options (in which case you force them to change their configuration/scripts/way to do things). |
| 15 |
|
| 16 |
Additionally, do you have any numbers about existing or new users and about the percentage, which |
| 17 |
would like the build output to be quiet? Otherwise i see such lines as guess and could say the same |
| 18 |
about the exact opposite view ;-) |
Archives