Mike Frysinger schrieb:
> On Saturday 12 November 2011 17:24:08 Patrick Lauer wrote:
>> On 11/11/11 16:44, Zac Medico wrote:
>>>> good point.  we don't want to punish old portage users.  let's enable it
>>>> by default in portage itself then.  just add `elog` output to the
>>>> portage ebuild to inform users of the change ?  or do we want a news
>>>> item ?
>>>>
>>>> what's the flag to negate the default ?  --no-quiet-build ? ;)
>>>
>>> It's --quiet-build=n. I've gone ahead and enabled it for release in
>>> portage-2.1.10.34:
>>>
>>> http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=0cc1
>>> 74b6fc28feb26ea151d76f794e0ff2c2fa39
>>
>> Lots of people in #gentoo are unhappy with it.
> 
> most changes people will be unhappy with because it's different
> 
>> Most devs will be unhappy as it makes it harder to view the log while
>> building.
> 
> devs are not the normal case.  it's trivial to have them use --quiet-build=n 
> in their default emerge opts.
> -mike

This can be argued from either side, if the default is verbose, you can make it 
quiet in the default
emerge opts and the other way round. So this is no argument for or against 
default quiet build in my
eyes.

As already said, it is nice to see, where a build hangs, when some specific 
task does take longer
and until now, it was easy to see, just watch the output. With the new default, 
you cannot say, what
it does, where it may be or if there are many things or just one line taking 
much time. And you
additionally have to go to the build.log manually to actually see something.
In addition, it is also nice to just a quick look into the console to see, what 
and where it failed.

Both points are probably not only usefull to devs, but also to many users, in 
addition to the point,
that changing the default emerge opts gets time consuming, when you have more 
than 1 or 2 machines.
Additionally, not every machine used by a dev will or should be using a dev/ 
profile, so changing
the default there will not fix the issue.

So i also vote for a revert of this. If you dont want to see the output for 
whatever reason, you can
still make it quiet, but i have not yet seen any reason to make it quiet by 
default for everyone.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to