| 1 |
On 11/14/2011 04:36 AM, Dale wrote: |
| 2 |
> Zac Medico wrote: |
| 3 |
>> 1) I estimate that the flooding of the terminal with build output is |
| 4 |
>> useless for more than 99% of users. Usually, there's too much |
| 5 |
>> information scrolling by at too high of a rate for it to be |
| 6 |
>> intelligible. Having this as the default behavior is ridiculous and |
| 7 |
>> leads to jokes like apt-gentoo [1]. Generally, people who want to |
| 8 |
>> analyze build output are best served by PORT_LOGDIR. |
| 9 |
> |
| 10 |
> One key. Scroll Lock. You can look all you want then hit it again to |
| 11 |
> let it carry on. There is also ctrl Z as well. I use that a good bit |
| 12 |
> to see what is going on. Just type in fg to carry on. |
| 13 |
> |
| 14 |
> As for progress, genlop -c does that already. |
| 15 |
|
| 16 |
We're not stopping you from using your preferred approach. Just set |
| 17 |
EMERGE_DEFAULT_OPTS="--quiet-build=n" in /etc/make.conf if it suits you. |
| 18 |
|
| 19 |
>> |
| 20 |
>> 2) With --quiet-build, the user is presented with a useful summary of |
| 21 |
>> overall progress, along with current load average data. The output is |
| 22 |
>> consistent regardless of whether or not the emerge --jobs option is used. |
| 23 |
>> |
| 24 |
>> [1] http://chris-lamb.co.uk/2011/08/12/careful-what-you-wish-for/ |
| 25 |
> |
| 26 |
> Unless you are trying to compile one that failed earlier. Then you |
| 27 |
> don't want the default, you want to see what made it fail. Then google |
| 28 |
> is our friend again. |
| 29 |
|
| 30 |
With --quiet-build, if a build fails then the *entire* build log is |
| 31 |
displayed on the terminal. |
| 32 |
-- |
| 33 |
Thanks, |
| 34 |
Zac |
Archives