From: Teresa and Dale <teendale@vista-express.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gcc upgrade, should it upgrade?
Date: Wed, 29 Mar 2006 10:24:32 -0600 [thread overview]
Message-ID: <442AB4C0.105@vista-express.com> (raw)
In-Reply-To: <442A499B.6030801@gmail.com>
Nagatoro wrote:
>Neil Bothwick wrote:
>
>
>>On Tue, 28 Mar 2006 20:41:14 -0800, Ryan Tandy wrote:
>>
>>
>>
>>>Assuming it's the gcc-3.4.5-r1 update you're considering postponing,
>>>you could just:
>>>
>>># echo '>sys-devel/gcc-3.4.5' >> /etc/portage/package.mask
>>>
>>>and just remove that line when you're ready to upgrade. It's a *far*
>>>better idea than trying to modify your profile.
>>>
>>>
>>echo '=sys-devel/gcc-3.4.5-r1' >> /etc/portage/package.mask is better if you only want to postpone this upgrade. Your suggestion blocks all future upgrades.
>>
>>
>>
>>
>
>Why don't upgrade? As far as I know upgrading gcc isn't a big deal. It
>was just the 3.3.x -> 3.4.x that was due to that the api for c++ had
>changed.
>
>
Oh, I thought it was a big deal. That's why I was wanting to wait.
Funny thing is, it don't want to upgrade now so maybe it had a bug and
they set it back again or something, or I just missed it and upgraded
anyway. ;-)
Dale
:-)
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-29 16:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 6:06 [gentoo-user] gcc upgrade, should it upgrade? Teresa and Dale
2006-03-28 8:04 ` Neil Bothwick
2006-03-28 12:24 ` Hemmann, Volker Armin
2006-03-28 15:50 ` Teresa and Dale
2006-03-28 16:14 ` Neil Bothwick
2006-03-29 4:33 ` Teresa and Dale
2006-03-29 4:41 ` Ryan Tandy
2006-03-29 5:10 ` Teresa and Dale
2006-03-29 13:27 ` Hemmann, Volker Armin
2006-03-29 8:21 ` Neil Bothwick
2006-03-29 8:47 ` Nagatoro
2006-03-29 16:24 ` Teresa and Dale [this message]
2006-03-29 17:26 ` Holly Bostick
2006-03-29 19:56 ` Teresa and Dale
2006-03-29 8:52 ` Keats
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=442AB4C0.105@vista-express.com \
--to=teendale@vista-express.com \
--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