public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: nunojsilva@ist.utl.pt (Nuno J. Silva)
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: gcc upgrade
Date: Wed, 14 Jul 2010 16:45:16 +0100	[thread overview]
Message-ID: <87vd8i9ier.fsf@ist.utl.pt> (raw)
In-Reply-To: 201007141652.39389.alan.mckinnon@gmail.com

Alan McKinnon <alan.mckinnon@gmail.com> writes:

> On Wednesday 14 July 2010 05:49:48 Valmor de Almeida wrote:
>> Mark Knecht wrote:
>> > On Sat, Jul 10, 2010 at 6:28 AM, Mark Knecht <markknecht@gmail.com> wrote:
>> >> On Sat, Jul 10, 2010 at 4:52 AM, Alan McKinnon <alan.mckinnon@gmail.com>
>> >> wrote: <SNIP>
>> >> 
>> >>> Unless he's the kind of guy who likes to rip his Ferrari apart for
>> >>> kicks and put it all back together again so that not even the factory
>> >>> can notice...
>> >> 
>> >> Precisely... :-)
>> > 
>> > Oh, and besides liking the smell of fresh baked 1 and 0's in the
>> > morning emerge -e @world was an easy  way to solve my libpng problem.
>> > Woke up this morning to a freshly baked Gentoo machine.
>> > 
>> > - Mark
>> 
>> Exactly. My Ferrari is back with a brand new engine and no libpng issue.
>
>
> Lets follow this logic.
>
> You blindly wanted to re-emerge all of world because an over-reaching gcc 
> upgrade guide said so. Coincidentally, there was a monumental libpng cock-up 
> hanging around which emerge -e world just happened to fix.

And which could have been solved with revdep-rebuild (or at least
running it here after removing the previous version solved it - I just
followed flameeyes guide).

Emerge -e was like buying a new car when it would have been cheaper and
easier to just replace the fault part(s).

-- 
Nuno J. Silva
gopher://sdf-eu.org/1/users/njsg




  reply	other threads:[~2010-07-14 15:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-10  1:16 [gentoo-user] gcc upgrade Valmor de Almeida
2010-07-10  0:57 ` [gentoo-user] " Nikos Chantziaras
     [not found]   ` <4C37C69F.4000700@gmail.com>
2010-07-10  1:24     ` Mark Knecht
2010-07-10  2:26       ` Dale
2010-07-10  2:32         ` Mark Knecht
2010-07-10  2:45     ` Valmor de Almeida
2010-07-10  3:02       ` walt
2010-07-10  9:32     ` Neil Bothwick
2010-07-10 11:52   ` Alan McKinnon
2010-07-10 13:28     ` Mark Knecht
2010-07-10 14:15       ` Mark Knecht
2010-07-10 16:30         ` Enrico Weigelt
2010-07-14  3:49         ` Valmor de Almeida
2010-07-14 14:52           ` Alan McKinnon
2010-07-14 15:45             ` Nuno J. Silva [this message]
2010-07-14  4:39         ` Valmor de Almeida
2010-07-14  3:50           ` Dale
2010-07-14  4:34             ` Mark Knecht
2010-07-14  5:00               ` Dale
2010-07-14  6:37             ` Valmor de Almeida
2010-07-14 14:48           ` Alan McKinnon
     [not found] <f4vXs-1cB-3@gated-at.bofh.it>
     [not found] ` <f4wAa-1Wt-3@gated-at.bofh.it>
     [not found]   ` <f4GSS-8pv-3@gated-at.bofh.it>
2010-07-12  8:18     ` ZekeyG
2010-07-12 19:44       ` Alan McKinnon
2010-07-12 20:52         ` Nuno J. Silva

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=87vd8i9ier.fsf@ist.utl.pt \
    --to=nunojsilva@ist.utl.pt \
    --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