public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Skwar <listen@alexander.skwar.name>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Upgrading to gcc 4.1 , question on recompiling
Date: Thu, 20 Jul 2006 18:47:18 +0200	[thread overview]
Message-ID: <44BFB396.1090506@mid.email-server.info> (raw)
In-Reply-To: <20060720000613.GA4807@sympatico.ca>

Philip Webb schrieb:

> A lot of outstanding bugs seem to affect only a few special users.

Like those, using KDE. But I wouldn't say, that those a just a
"few".

> Yet again, Gentoo should make a 4th category by making "stable" = "server"
> & splitting "testing" into "newly unmasked" & "desktop-ready":

Why? ~ is testing. The only problem I had, which caused me to
start the short thread, was, that the gcc upgrade doc *used to*
say, that upgrading from gcc 3.4.x to 4.1.x implied no risk.

> many "testing" packages today are in fact desktop-ready,
> ie the remaining bugs will be rare & easy to recover from.

Yep, quite easy to recover - recompile everything.

Alexander Skwar
-- 
Adam and Eve had many advantages, but the principal one was, that they escaped
teething.
		-- Mark Twain, "Pudd'nhead Wilson's Calendar"
-- 
gentoo-user@gentoo.org mailing list



      parent reply	other threads:[~2006-07-20 16:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060719105701.59255.qmail@web61014.mail.yahoo.com>
2006-07-19 12:30 ` [gentoo-user] Upgrading to gcc 4.1 , question on recompiling Alexander Skwar
2006-07-19 13:05   ` Philip Webb
2006-07-19 13:20     ` [gentoo-user] " Sven Köhler
2006-07-19 13:34     ` [gentoo-user] " Alexander Skwar
2006-07-19 13:51       ` Richard Broersma Jr
2006-07-19 13:57         ` Alexander Skwar
2006-07-19 14:22       ` Neil Bothwick
2006-07-20  0:06         ` Philip Webb
2006-07-20  8:02           ` Neil Bothwick
2006-07-20 16:47           ` Alexander Skwar [this message]

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=44BFB396.1090506@mid.email-server.info \
    --to=listen@alexander.skwar.name \
    --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