| 1 |
Andrew Muraco wrote: |
| 2 |
> Mark Loeser wrote: |
| 3 |
>> Andrew Muraco <tuxp3@×××××××××.com> said: |
| 4 |
>>> is a minimum. A full out doc with all the FAQ and important notes |
| 5 |
>>> about what needs to be recompiled (in my opinion) would be a much |
| 6 |
>>> more through upgrade path, ofcourse still include the einfo quick |
| 7 |
>>> instructions. But I think the masses of users will not be happy when |
| 8 |
>>> they realize that emerge -e world && emerge -e world means that they |
| 9 |
>>> will be compiling for the next day (or 2 or 3), so a way to block the |
| 10 |
>>> upgrade from messing up people that wish to keep 3.3.x as default |
| 11 |
>>> would be a good idea. |
| 12 |
>>> |
| 13 |
>> |
| 14 |
>> gcc-3.4.* will not be selected as your system compiler after merging |
| 15 |
>> it. The |
| 16 |
>> old gcc profile is still valid, therefore it is kept. Users have to |
| 17 |
>> consciously go and change their profile to change their gcc, so |
| 18 |
>> 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 |
All arches other than x86 have made the switch to 3.4 stable already. They did |
| 26 |
so without problem and without extra docs. Why does x86, the last to switch, |
| 27 |
need to be special-cased? |
| 28 |
|
| 29 |
|
| 30 |
--de. |
| 31 |
|
| 32 |
-- |
| 33 |
gentoo-dev@g.o mailing list |
Archives