Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Dale <rdalek1967@...>
Subject: Re: Re: have portage be quiet by default
Date: Mon, 14 Nov 2011 06:36:45 -0600
Zac Medico wrote:
> On 11/13/2011 08:24 AM, Duncan wrote:
>> The previous defaults made perfect sense to me already.  Parallel emerge
>> jobs already puts portage in quiet mode, and that's what most people who
>> care (see my point above about whether this is the right distro choice or
>> not) should already be using.  That default makes sense, since otherwise
>> the output would be jumbled anyway.
>>
>> 1-at-a-time merge defaults are therefore where the question is.  Two
>> positions could be taken here.  If it is argued that those who care will
>> already be using parallel mode in most cases, and that those who care but
>> that can't be bothered to switch their defaults really should be
>> questioning whether gentoo is an appropriate choice in the first place,
>> then a "noisy" default for 1-at-a-time makes sense too, because the only
>> time most (who care) will see it is when they're actually troubleshooting
>> something and thus deliberately using 1-at-a-time mode, in which case the
>> higher level of detail by default for that mode makes the the most sense.
> Ever since I added --jobs support, I've felt that suppression of build
> output would be a better default for at least the following reasons:
>
> 1) I estimate that the flooding of the terminal with build output is
> useless for more than 99% of users. Usually, there's too much
> information scrolling by at too high of a rate for it to be
> intelligible. Having this as the default behavior is ridiculous and
> leads to jokes like apt-gentoo [1]. Generally, people who want to
> analyze build output are best served by PORT_LOGDIR.

One key.  Scroll Lock.  You can look all you want then hit it again to 
let it carry on.  There is also ctrl Z as well.  I use that a good bit 
to see what is going on.  Just type in fg to carry on.

As for progress, genlop -c does that already.
>
> 2) With --quiet-build, the user is presented with a useful summary of
> overall progress, along with current load average data. The output is
> consistent regardless of whether or not the emerge --jobs option is used.
>
> [1] http://chris-lamb.co.uk/2011/08/12/careful-what-you-wish-for/

Unless you are trying to compile one that failed earlier.  Then you 
don't want the default, you want to see what made it fail.  Then google 
is our friend again.

That said, GREAT work on portage.  :-D

Dale

:-)  :-)


Replies:
Re: Re: have portage be quiet by default
-- Zac Medico
References:
[RFC] enable verbose build whenever it's possible
-- Kacper Kowalik
Re: have portage be quiet by default
-- Zac Medico
Re: have portage be quiet by default
-- Patrick Lauer
Re: have portage be quiet by default
-- Mike Frysinger
Re: have portage be quiet by default
-- Thomas Sachau
Re: have portage be quiet by default
-- Amadeusz Żołnowski
Re: have portage be quiet by default
-- Duncan
Re: Re: have portage be quiet by default
-- Zac Medico
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Re: have portage be quiet by default
Next by thread:
Re: Re: have portage be quiet by default
Previous by date:
Re: have portage be quiet by default
Next by date:
Re: have portage be quiet by default


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.