| 1 |
On Sun, Nov 13, 2011 at 05:59:21PM -0800, Zac Medico wrote: |
| 2 |
> Well, it's much easier to gather interest and get feedback if we deploy |
| 3 |
> the change and ask questions later. |
| 4 |
|
| 5 |
What if we tried solving this problem by providing more options instead |
| 6 |
of trying to guess what the users want? :) |
| 7 |
|
| 8 |
Imagine the following output (when jobs == 1): |
| 9 |
|
| 10 |
>>> Verifying ebuild manifests |
| 11 |
>>> Emerging (1 of 1) www-client/chromium-16.0.912.36 |
| 12 |
>>> Quiet building enabled. Enable for [P]ackage or [S]ession. [L]earn more. |
| 13 |
>>> Jobs: 0 of 1 complete, 1 running Load avg: 0.23, 0.18, 0.10 |
| 14 |
|
| 15 |
Pressing P would only show the log for the actively built package. |
| 16 |
Pressing S would show all the logs for this session, starting with the |
| 17 |
active one. |
| 18 |
|
| 19 |
Pressing L would print out a short set of instructions, something |
| 20 |
like: |
| 21 |
|
| 22 |
"To make portage output easier to track and understand, --quiet-build |
| 23 |
has been enabled by default. You may restore the old, verbose behavior |
| 24 |
temporarily by using the P and S commands, or permanently by adding |
| 25 |
'--quiet-build=n' to your make.conf's EMERGE_DEFAULT_OPTS." |
| 26 |
|
| 27 |
I believe many users would appreciate the ability to output logs on |
| 28 |
demand. :) |
| 29 |
-- |
| 30 |
Alex Alexander | wired |
| 31 |
+ Gentoo Linux Developer |
| 32 |
++ www.linuxized.com |
Archives