public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] One machine sends "emerge" text output to stderr, not stdout
Date: Wed, 17 Nov 2010 19:20:25 -0500	[thread overview]
Message-ID: <20101118002025.GA23732@waltdnes.org> (raw)
In-Reply-To: <D1C3B1A2-61F3-4745-8F7C-D6C1ED71EDE7@stellar.eclipse.co.uk>

On Wed, Nov 17, 2010 at 01:41:45PM +0000, Stroller wrote

> It's probably fixed in one of the updates! Why are you posting before
> you checked that!?!?

  It started happening suddenly  And yes, I did search bugzilla,
although I admit my searches aren't always perfect.  And if "emerge
--sync"  output ends up telling me there is a portage update, I do run
it first.

> > The main quirk on my mcahines is that I start USE with "-*" on all my
> > machines.  This goes back to when the developers "in their infinite
> > wisdom", decided to make ipv6 a default USE flag.
> 
> Why not just use -ipv6 as a global USE flag!?!? 
> 
> I have to admit that the Gentoo devs have in the past made decisions
> which have caused me to be suspicious of their sanity. But if I
> disagree with them over a USE flag I just add it to make.conf.

  Because I don't want a repeat of the ipv6 fiasco where I had an almost
non-functional browser, mediaplayer (for internet files), etc, etc.  And
I also had to run "emerge --newuse --update world" and inspect the
output from "emerge -pv --depclean" and remove additional stuff, and
then revdep-rebuild to clean up the resulting extra "goodies".  If I
don't use "-*" what's the next flag that the devs will add?  And how many
of my current packages will link against it?

  On occasion, "emerge -pv --deep --update world" will complain that a
certain USE flag is required for my config.  At that time, I will decide
if I really want the package that requires the flag, and if so, whether
to enable the flag globally or one-off in /etc/package.use

  OK, so I'm a control freak.  That's one reason I left Windows.  I want
to be in charge of my machine.

-- 
Walter Dnes <waltdnes@waltdnes.org>



  reply	other threads:[~2010-11-18  0:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17  0:25 [gentoo-user] One machine sends "emerge" text output to stderr, not stdout Walter Dnes
2010-11-17  1:20 ` Adam Carter
2010-11-17 13:41 ` Stroller
2010-11-18  0:20   ` Walter Dnes [this message]
2010-11-18  0:51     ` Alan McKinnon
2010-11-18  4:46     ` Stroller
2010-11-18 11:25       ` Neil Bothwick
2010-11-18 13:24         ` Vincent Launchbury
2010-11-18 14:27         ` [gentoo-user] tmux vs. screen Stroller
2010-11-18 19:52           ` Paul Hartman
2010-11-18 22:25             ` Florian CROUZAT
2010-11-18 22:44               ` Alan McKinnon
2010-11-18 23:36                 ` Dale
2010-11-19 10:33                   ` Jesús J. Guerrero Botella
2010-11-18 11:21     ` [gentoo-user] One machine sends "emerge" text output to stderr, not stdout Neil Bothwick
2010-11-19  6:34       ` Walter Dnes
2010-11-19  7:21         ` Dale
2010-11-19  9:25         ` Neil Bothwick
2010-11-20  5:32           ` Walter Dnes
2010-11-20 15:04             ` Neil Bothwick

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=20101118002025.GA23732@waltdnes.org \
    --to=waltdnes@waltdnes.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