| 1 |
On 07/09/12 14:24, Tanstaafl wrote: |
| 2 |
> This has never happened to me before... |
| 3 |
> |
| 4 |
> Since when did a simple GCC upgrade *automatically* REMOVE my prior GCC |
| 5 |
> install??? |
| 6 |
> |
| 7 |
> I have *always* kept my prior GCC around for a while, if not until the |
| 8 |
> next upgrade, just as something to fall back on if the current one breaks. |
| 9 |
> |
| 10 |
> I am NOT a happy camper. |
| 11 |
|
| 12 |
It has always been that way for packages in the same slot. 4.5.3 and |
| 13 |
4.5.4 are both in the "4.5" slot. I think you're confusing |
| 14 |
patch-version upgrades with major and minor-version ones. If you emerge |
| 15 |
GCC 4.6.3, your 4.5.4 version will be kept. |
| 16 |
|
| 17 |
If you really wont to keep multiple patch-versions, then you must set |
| 18 |
the "multislot" USE flag for GCC. But unless you have a reason to do |
| 19 |
that, and it seems you don't, there's no reason to have multiple such |
| 20 |
versions installed. |
Archives