| 1 |
Excerpts from Thomas Sachau's message of 2011-11-13 14:59:57 +0100: |
| 2 |
> How is that an argument for default quiet build? It is exactly the |
| 3 |
> same argument against default quiet build. If someone does not care, |
| 4 |
> he does not care about the output being verbose or not, so no need to |
| 5 |
> change a default for him. |
| 6 |
|
| 7 |
As I have written below, information about overall process is more |
| 8 |
valuable than some gmake rubbish (to the user) output which slows down |
| 9 |
build time. And having that shinny human readable output gives actually |
| 10 |
an information to the reader. |
| 11 |
|
| 12 |
|
| 13 |
> And what does a number of users knowing about an option have to do |
| 14 |
> with a default setting? |
| 15 |
|
| 16 |
More user-friendly options should be default, not developer-friendly. |
| 17 |
The discussion started with problem, that build.log could be more |
| 18 |
verbose, which will clutter users' screen even more. |
| 19 |
|
| 20 |
|
| 21 |
> You expect people to manually check the build.log just to see, where |
| 22 |
> it hangs? I prefer checking the console, there i can see it directly |
| 23 |
> and dont have to check for the path of the current build.log and then |
| 24 |
> have to additionally open it manually. So your "no harm" is plain |
| 25 |
> wrong, since it takes me more time for doing the same thing as before, |
| 26 |
> while i still see no benefit for the change of the default. |
| 27 |
|
| 28 |
If you need to watch build output, change defaults. Defaults are for |
| 29 |
less experienced users, not for us developers or power users. |
| 30 |
|
| 31 |
|
| 32 |
> > But --quiet-build=y actually gives more useful and handy info: what |
| 33 |
> > is a total progress. Which user cares about which module is |
| 34 |
> > actually being compiled? He/she cares more which package out of |
| 35 |
> > total is being compiled at the moment. |
| 36 |
> |
| 37 |
> If someone does not care about the current state of a compile, he wont |
| 38 |
> care about the total state either. |
| 39 |
|
| 40 |
Build output hardly ever says about current state of a compile. If you |
| 41 |
can tell from the output how much is left for example for firefox - |
| 42 |
respect. |
| 43 |
|
| 44 |
|
| 45 |
> Beside the point, that you can see the total state in the terminal bar |
| 46 |
> (i hope, i got the right name for that thing). |
| 47 |
|
| 48 |
This not always work. |
| 49 |
|
| 50 |
|
| 51 |
-- |
| 52 |
Amadeusz Żołnowski |
Archives