public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] pet peeve: sending normal output to stderr (env-update)
Date: Tue, 14 Nov 2006 13:45:58 -0700	[thread overview]
Message-ID: <7573e9640611141245w456ee863yde01fdf8c268156@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0611140948000.23548@atlantis.flyingjoke.org>

On 11/14/06, David Talkington <dtalk@prairienet.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Why on earth does env-update send this:
>
> >>> Regenerating /etc/ld.so.cache...

env-update.sh outputs this message with a simple "echo", so no output
to stdout here.  However portage writes most ">>>" messages to stderr.

You can either file a bug report on bugs.gentoo.org to try and get the
behavior changed, or use "emerge ... 2>&1 >/dev/null | grep -v -e '>>>
Regenerating '".  This will send stdout to /dev/null, and stderr to
the pipe where grep can filter out whatever messages annoy you.

-Richard
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-11-14 20:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14 17:50 [gentoo-user] pet peeve: sending normal output to stderr (env-update) David Talkington
2006-11-14 18:30 ` Glenn McCarthy
2006-11-14 20:45 ` Richard Fish [this message]
2006-11-14 21:40   ` [gentoo-user] [OT] " Daniel Iliev
2006-11-14 22:21     ` Etaoin Shrdlu
2006-11-14 22:27       ` Daniel Iliev
2006-11-16 18:49   ` [gentoo-user] " David Talkington
2006-11-16 20:56     ` Richard Fish
2006-11-16 21:53       ` Bo Ørsted Andresen

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=7573e9640611141245w456ee863yde01fdf8c268156@mail.gmail.com \
    --to=bigfish@asmallpond.org \
    --cc=gentoo-user@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