| 1 |
On 14 November 2011 03:25, Alex Alexander <wired@g.o> wrote: |
| 2 |
> On Sun, Nov 13, 2011 at 05:59:21PM -0800, Zac Medico wrote: |
| 3 |
>> Well, it's much easier to gather interest and get feedback if we deploy |
| 4 |
>> the change and ask questions later. |
| 5 |
> |
| 6 |
> What if we tried solving this problem by providing more options instead |
| 7 |
> of trying to guess what the users want? :) |
| 8 |
> |
| 9 |
> Imagine the following output (when jobs == 1): |
| 10 |
> |
| 11 |
>>>> Verifying ebuild manifests |
| 12 |
>>>> Emerging (1 of 1) www-client/chromium-16.0.912.36 |
| 13 |
>>>> Quiet building enabled. Enable for [P]ackage or [S]ession. [L]earn more. |
| 14 |
>>>> Jobs: 0 of 1 complete, 1 running Load avg: 0.23, 0.18, 0.10 |
| 15 |
> |
| 16 |
> Pressing P would only show the log for the actively built package. |
| 17 |
> Pressing S would show all the logs for this session, starting with the |
| 18 |
> active one. |
| 19 |
> |
| 20 |
> Pressing L would print out a short set of instructions, something |
| 21 |
> like: |
| 22 |
> |
| 23 |
> "To make portage output easier to track and understand, --quiet-build |
| 24 |
> has been enabled by default. You may restore the old, verbose behavior |
| 25 |
> temporarily by using the P and S commands, or permanently by adding |
| 26 |
> '--quiet-build=n' to your make.conf's EMERGE_DEFAULT_OPTS." |
| 27 |
> |
| 28 |
> I believe many users would appreciate the ability to output logs on |
| 29 |
> demand. :) |
| 30 |
> -- |
| 31 |
> Alex Alexander | wired |
| 32 |
> + Gentoo Linux Developer |
| 33 |
> ++ www.linuxized.com |
| 34 |
> |
| 35 |
|
| 36 |
IMO, that is *THE PERFECT* solution. It requires writing a significant |
| 37 |
amount of code (i'd bet), but IMO, that's perfect and i think all the |
| 38 |
rest of the detractors and most of the people in favour of |
| 39 |
--quiet-build=y would be happy with that solution. |
| 40 |
|
| 41 |
Another idea I had which is also difficult to implement but would |
| 42 |
somewhat solve the "screen full of configure/make output" is to (in |
| 43 |
portage) basically parse the output of verbose buildsystems and |
| 44 |
reformat them to look like the output of say AutoMake's silent-rules |
| 45 |
or CMake. That way each line is like "CC" + filename, as opposed to a |
| 46 |
couple hundred character line full of the entire GCC command. |
| 47 |
|
| 48 |
I'd prefer Alex's suggestion though. |
Archives