| 1 |
On Tue, 28 Mar 2006 00:06:54 -0600, Teresa and Dale wrote: |
| 2 |
|
| 3 |
> I upgraded gcc a while back. I thought I read somewhere that it is best |
| 4 |
> to just upgrade on occasion with the major upgrades. Should this be |
| 5 |
> upgraded or should I mask it? This is what I get: |
| 6 |
> |
| 7 |
> > root@smoker / # emerge -up world |
| 8 |
> > |
| 9 |
> > These are the packages that I would merge, in order: |
| 10 |
> > |
| 11 |
> > Calculating world dependencies ...done! |
| 12 |
> > [ebuild U ] sys-devel/gcc-config-1.3.13-r1 [1.3.12-r6] |
| 13 |
> > [ebuild U ] sys-devel/gcc-3.4.5-r1 [3.4.5] |
| 14 |
|
| 15 |
Read the changelog and decide for yourself. |
| 16 |
"emerge --changelog gcc" will show you the changes and the reason for |
| 17 |
the upgrade. |
| 18 |
|
| 19 |
> I really don't want to do a emerge -e world or rebuild a lot right now. |
| 20 |
> I am glad to see the new Scribus though. ;-) |
| 21 |
|
| 22 |
You don't have to do an emerge -e- world for a minor update to GCC. Maybe |
| 23 |
when you go from 3.3 to 3.4, or 3.4 to 4.0, but not for this. |
| 24 |
|
| 25 |
|
| 26 |
-- |
| 27 |
Neil Bothwick |
| 28 |
|
| 29 |
Bookmark - A means of returning to where you got lost last time. |
Archives