From: Thomas de Grenier de Latour <degrenier@easyconnect.fr>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: epause instead of sleep in ebuilds
Date: Sat, 4 Sep 2004 08:49:19 +0200 [thread overview]
Message-ID: <20040904084919.086829df@eusebe> (raw)
In-Reply-To: <4138B529.9060500@gentoo.org>
On Fri, 03 Sep 2004 20:17:13 +0200
Simon Stelling <blubb@gentoo.org> wrote:
> I think it's much easier and more user-friendly to make emerge
> less verbose
You can give a try to my patch in bug #37491, I've updated it for
last portage pre-release, and making emerge a bit quiet was its
exact purpose.
> * Applying ncurses-5.4-xterm.patch...
> * Applying ncurses-5.4-share-sed.patch...
Imho, this ones should not be shown to user. With my patch, such
messages could be changed from "einfo" to "veinfo", which looks
the same but only display in verbose output/log. Since they are
mostly in a few eclasses, that would not be to much work to make
this cleanup.
> of course this is not fine if you have a package that failed to
> emerge, but caching the last X lines and printing it in case of
> an error would be a nice workaround
What I do is that if emerge is in quiet mode, and the user don't
uses PORT_LOGDIR, then there will still be a verbose log in ${T}.
And "die" messages point to this log. (see the 2nd screenshot in
the bug report)
> -v could be used to get the old-fashioned style.
With my patch, default behavior is still to be verbose, but if
"quiet" is in feature flags (or on command line options). And yes,
in all case, -v forces verbose mode.
--
TGL.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-09-04 6:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 20:21 [gentoo-dev] rfc: epause instead of sleep in ebuilds Ciaran McCreesh
2004-09-01 20:40 ` Karl Trygve Kalleberg
2004-09-01 20:43 ` Ciaran McCreesh
2004-09-02 7:02 ` Alexander Gretencord
2004-09-02 7:43 ` Dice R. Random
2004-09-02 13:30 ` Mike Frysinger
2004-09-02 18:03 ` Alexander Gretencord
2004-09-02 18:51 ` Mike Doty
2004-09-02 20:03 ` N. Owen Gunden
2004-09-03 12:21 ` Paul de Vrieze
2004-09-03 18:17 ` Simon Stelling
2004-09-04 6:49 ` Thomas de Grenier de Latour [this message]
2004-09-01 20:49 ` Seemant Kulleen
2004-09-01 21:29 ` Ciaran McCreesh
2004-09-01 22:10 ` Tavis Ormandy
2004-09-01 22:41 ` Michael Sterrett -Mr. Bones.-
2004-09-02 13:05 ` Guillaume Destuynder
2004-09-02 13:49 ` Mamoru KOMACHI
2004-09-02 13:56 ` Ciaran McCreesh
2004-09-01 21:09 ` Chris Gianelloni
2004-09-01 21:17 ` Tavis Ormandy
2004-09-01 22:27 ` Mike Frysinger
2004-09-02 0:22 ` Ciaran McCreesh
2004-09-02 3:09 ` Brian Harring
2004-09-02 3:16 ` Mike Frysinger
2004-09-03 18:39 ` Lisa Seelye
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040904084919.086829df@eusebe \
--to=degrenier@easyconnect.fr \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox