1 |
Amadeusz Żołnowski schrieb: |
2 |
> Excerpts from Thomas Sachau's message of 2011-11-13 13:39:17 +0100: |
3 |
>> This can be argued from either side, if the default is verbose, you |
4 |
>> can make it quiet in the default emerge opts and the other way round. |
5 |
>> So this is no argument for or against default quiet build in my eyes. |
6 |
> |
7 |
> Not every user studies manpages of every program they use. Making |
8 |
> --quiet-build=y default is a *benefit* for people who don't care much. |
9 |
> If somebody cares about the output probably will care to read the |
10 |
> manpage how to make it verbose. How many emerge users know that option? |
11 |
|
12 |
How is that an argument for default quiet build? It is exactly the same argument against default |
13 |
quiet build. If someone does not care, he does not care about the output being verbose or not, so no |
14 |
need to change a default for him. |
15 |
And what does a number of users knowing about an option have to do with a default setting? |
16 |
> |
17 |
> |
18 |
>> As already said, it is nice to see, where a build hangs, when some |
19 |
>> specific task does take longer and until now, it was easy to see, just |
20 |
>> watch the output. With the new default, you cannot say, what it does, |
21 |
>> where it may be or if there are many things or just one line taking |
22 |
>> much time. And you additionally have to go to the build.log manually |
23 |
>> to actually see something. |
24 |
> |
25 |
> Build output tells almost nothing about the progress (except of cmake). |
26 |
> Many packages compile in few minutes on average machine. I hardly ever |
27 |
> experience hangs and if - it's usually for boost. For those few |
28 |
> packages it's no harm to check build.log. |
29 |
|
30 |
You expect people to manually check the build.log just to see, where it hangs? I prefer checking the |
31 |
console, there i can see it directly and dont have to check for the path of the current build.log |
32 |
and then have to additionally open it manually. So your "no harm" is plain wrong, since it takes me |
33 |
more time for doing the same thing as before, while i still see no benefit for the change of the |
34 |
default. |
35 |
|
36 |
> |
37 |
> But --quiet-build=y actually gives more useful and handy info: what is |
38 |
> a total progress. Which user cares about which module is actually being |
39 |
> compiled? He/she cares more which package out of total is being |
40 |
> compiled at the moment. |
41 |
|
42 |
If someone does not care about the current state of a compile, he wont care about the total state |
43 |
either. Beside the point, that you can see the total state in the terminal bar (i hope, i got the |
44 |
right name for that thing). |