On 11/13/2011 03:09 PM, Thomas Sachau wrote:
> Zac Medico schrieb:
>> On 11/13/2011 07:49 AM, Thomas Sachau wrote:
>>> Please give me a good reason, why i should by default do more things (adding quiet-build=n to the
>>> default emerge opts or searching for and opening the build.log) and what i or others do get from
>>> that. And less lines on the screen is no added value for me, it removes value.
>>
>> Why should we expose new users to legacy defaults that are useless to
>> more than 99% users, when they would most likely prefer the
>> --quiet-build display?
> 
> Why should we change the default behaviour for existing users? Those, who dont want to see it,
> probably already use --jobs or quiet-build=y. For the rest, they either dont know about those
> options (which does not get better, if some default behaviour changes) or they dont want those
> options (in which case you force them to change their configuration/scripts/way to do things).

When we change defaults, it affects everyone who hasn't yet overridden
the setting in EMERGE_DEFAULT_OPTS. That's just how it is.

> Additionally, do you have any numbers about existing or new users and about the percentage, which
> would like the build output to be quiet?

All I have is the feedback from this mailing list, an my own intuition.
My intuition says that --quiet-build is reasonable default that the
silent majority of people will welcome.

> Otherwise i see such lines as guess and could say the same
> about the exact opposite view ;-)

Well, my interpretation of this thread says that the response is
overwhelmingly positive, but I could be biased. ;)
-- 
Thanks,
Zac