| 1 |
Mark Loeser wrote: |
| 2 |
|
| 3 |
>Andrew Muraco <tuxp3@×××××××××.com> said: |
| 4 |
> |
| 5 |
> |
| 6 |
>>is a minimum. A full out doc with all the FAQ and important notes about |
| 7 |
>>what needs to be recompiled (in my opinion) would be a much more through |
| 8 |
>>upgrade path, ofcourse still include the einfo quick instructions. But I |
| 9 |
>>think the masses of users will not be happy when they realize that |
| 10 |
>>emerge -e world && emerge -e world means that they will be compiling for |
| 11 |
>>the next day (or 2 or 3), so a way to block the upgrade from messing up |
| 12 |
>>people that wish to keep 3.3.x as default would be a good idea. |
| 13 |
>> |
| 14 |
>> |
| 15 |
> |
| 16 |
>gcc-3.4.* will not be selected as your system compiler after merging it. The |
| 17 |
>old gcc profile is still valid, therefore it is kept. Users have to |
| 18 |
>consciously go and change their profile to change their gcc, so nothing is |
| 19 |
>going to just magically break. |
| 20 |
> |
| 21 |
That makes me feel a bit more comfortable. I still think that something |
| 22 |
more then an einfo warning should be provided, as its easy to overlook |
| 23 |
those. |
| 24 |
|
| 25 |
Tux |
| 26 |
-- |
| 27 |
gentoo-dev@g.o mailing list |
Archives