1 |
Mike Frysinger schrieb: |
2 |
> On Saturday 12 November 2011 17:24:08 Patrick Lauer wrote: |
3 |
>> On 11/11/11 16:44, Zac Medico wrote: |
4 |
>>>> good point. we don't want to punish old portage users. let's enable it |
5 |
>>>> by default in portage itself then. just add `elog` output to the |
6 |
>>>> portage ebuild to inform users of the change ? or do we want a news |
7 |
>>>> item ? |
8 |
>>>> |
9 |
>>>> what's the flag to negate the default ? --no-quiet-build ? ;) |
10 |
>>> |
11 |
>>> It's --quiet-build=n. I've gone ahead and enabled it for release in |
12 |
>>> portage-2.1.10.34: |
13 |
>>> |
14 |
>>> http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=0cc1 |
15 |
>>> 74b6fc28feb26ea151d76f794e0ff2c2fa39 |
16 |
>> |
17 |
>> Lots of people in #gentoo are unhappy with it. |
18 |
> |
19 |
> most changes people will be unhappy with because it's different |
20 |
> |
21 |
>> Most devs will be unhappy as it makes it harder to view the log while |
22 |
>> building. |
23 |
> |
24 |
> devs are not the normal case. it's trivial to have them use --quiet-build=n |
25 |
> in their default emerge opts. |
26 |
> -mike |
27 |
|
28 |
This can be argued from either side, if the default is verbose, you can make it quiet in the default |
29 |
emerge opts and the other way round. So this is no argument for or against default quiet build in my |
30 |
eyes. |
31 |
|
32 |
As already said, it is nice to see, where a build hangs, when some specific task does take longer |
33 |
and until now, it was easy to see, just watch the output. With the new default, you cannot say, what |
34 |
it does, where it may be or if there are many things or just one line taking much time. And you |
35 |
additionally have to go to the build.log manually to actually see something. |
36 |
In addition, it is also nice to just a quick look into the console to see, what and where it failed. |
37 |
|
38 |
Both points are probably not only usefull to devs, but also to many users, in addition to the point, |
39 |
that changing the default emerge opts gets time consuming, when you have more than 1 or 2 machines. |
40 |
Additionally, not every machine used by a dev will or should be using a dev/ profile, so changing |
41 |
the default there will not fix the issue. |
42 |
|
43 |
So i also vote for a revert of this. If you dont want to see the output for whatever reason, you can |
44 |
still make it quiet, but i have not yet seen any reason to make it quiet by default for everyone. |