Re: [gentoo-dev] have portage be quiet by default

[Patrick Lauer]

On 11/14/11 09:25, Alex Alexander wrote:
> On Sun, Nov 13, 2011 at 05:59:21PM -0800, Zac Medico wrote:
>> Well, it's much easier to gather interest and get feedback if we deploy
>> the change and ask questions later.
> What if we tried solving this problem by providing more options instead
> of trying to guess what the users want? :)
>
> Imagine the following output (when jobs == 1):
>
>>>> Verifying ebuild manifests
>>>> Emerging (1 of 1) www-client/chromium-16.0.912.36
>>>> Quiet building enabled. Enable for [P]ackage or [S]ession. [L]earn more.
>>>> Jobs: 0 of 1 complete, 1 running                Load avg: 0.23, 0.18, 0.10
> Pressing P would only show the log for the actively built package.
> Pressing S would show all the logs for this session, starting with the
> active one.
>
> Pressing L would print out a short set of instructions, something
> like:
>
> "To make portage output easier to track and understand, --quiet-build
> has been enabled by default. You may restore the old, verbose behavior
> temporarily by using the P and S commands, or permanently by adding
> '--quiet-build=n' to your make.conf's EMERGE_DEFAULT_OPTS."
>
> I believe many users would appreciate the ability to output logs on
> demand. :)
Interactive stuff is a bad idea. Please don't make me figure out ways to 
interactively stab you ;)
(I already spent so much time getting interactive ebuilds into a 
manageable state, and that was a more futile discussion than this one)

Why do y'all want to make it harder for me to figure out

1) is it just slow at compiling or stuck in a loop?
2) did it compile with proper settings ( just because the ebuild 
finished with exit code 0 doesn't mean it's correct - yesterday I had to 
turn off quiet-build and re-compile squashfs-tools just to see if the 
build output was as expected)
3) did it install the files I expected it to install? (hmm, why don't I 
have the "znurgh" binary now?!)

Not all failures are detected build failures ...

And handling it over EMERGE_DEFAULT_OPTS is also ugly, if I had anything 
else in there I'd find it quite annoying to figure out how to keep --ask 
--keep-going while disabling --quiet-build selectively.
So it'd be nicer to have a PORTAGE_QUIET_BUILD or similar var in 
make.conf - and still I'm annoyed that I have to spend time unbreaking 
the defaults.

Can we please get this reset to "classic mode" and not try to innovate 
things that worked perfectly well the last decade?


Patrick