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] Remerge the system with gcc-4.1?
Date: Fri, 8 Sep 2006 00:22:51 -0700	[thread overview]
Message-ID: <7573e9640609080022g1860b67flc2cfd304ad5e58e0@mail.gmail.com> (raw)
In-Reply-To: <45010AC8.5080807@home.se>

On 9/7/06, Erik <sigra@home.se> wrote:
> Grant wrote:
> > Does gcc-4.1 offer enough of an improvement to warrant remerging the
> > whole system?
> No, just remerge the packages that need to be remerged. Then emerge the
> rest with gcc-4.1 when updates come.

Why do you advise people to ignore the official gcc upgrade
documentation and potentially break their systems?  Safely performing
the gcc upgrade *requires* an emerge -e world.  Your system /might/
not break without that, and you are free to take that risk for your
systems, but please do *not* recommend that others take on such risks.

If you want to tell people your experiences, that's great, but be sure
to separate the "what is recommended" from "what worked for me".

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



  parent reply	other threads:[~2006-09-08  7:30 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49bf44f10609072007w4c110d77je1152ea578c7e708@mail.gmail.com>
2006-09-08  6:16 ` [gentoo-user] Remerge the system with gcc-4.1? Erik
2006-09-08  6:26   ` Boris Fersing
2006-09-08  7:09     ` jarry
2006-09-08 11:56       ` Timothy A. Holmes
2006-09-08 12:24         ` Dale
2006-09-08 13:11           ` Jean-Marc Beaune
2006-09-08 15:44             ` michael
2006-09-11 15:58               ` Matthias Bethke
2006-09-08 14:24         ` Grant
2006-09-08 14:33           ` Michael Crute
2006-09-09  0:40             ` Mark Kirkwood
2006-09-08 14:37           ` Andrew Gaydenko
2006-09-08 14:59             ` Neil Bothwick
2006-09-08 15:26               ` Andrew Gaydenko
2006-09-08 16:05                 ` Neil Bothwick
2006-09-08 16:18                   ` Andrew Gaydenko
2006-09-08 15:12           ` Timothy A. Holmes
2006-09-08 15:30             ` Jean-Marc Beaune
2006-09-08 15:45               ` michael
2006-09-08 17:02             ` Bo Ørsted Andresen
2006-09-08 17:09               ` Timothy A. Holmes
2006-09-08 17:35                 ` Bo Ørsted Andresen
2006-09-08 18:07                   ` Timothy A. Holmes
2006-09-08 19:05                     ` Bo Ørsted Andresen
2006-09-08 19:49           ` Richard Fish
2006-09-08 20:10             ` Timothy A. Holmes
2006-09-08 20:29               ` Richard Fish
2006-09-08  7:22   ` Richard Fish [this message]
2006-09-08 21:34     ` [gentoo-user] " Peter
2006-09-08 22:12       ` Richard Fish
2006-09-08 22:20         ` Peter
2007-10-10  5:39         ` Daevid Vincent
2007-10-10  5:51           ` Mark Kirkwood
2007-10-10 22:32           ` Mick
2006-09-08 21:35     ` Peter
2006-09-08  6:23 ` [gentoo-user] " Dirk Heinrichs

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=7573e9640609080022g1860b67flc2cfd304ad5e58e0@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