1 |
i dont plan on suggesting any gcc-4.2 version for stable. arches of course |
2 |
are free to determine if gcc-4.2 works better for them than gcc-4.1 and thus |
3 |
move to stable. |
4 |
|
5 |
gcc-4.3 seems to be standing up well. since the major gcc-ebuild-specific |
6 |
issues seem to be resolved now, i'll probably do a sweep of bugs to see if |
7 |
there's any patches i'm missing (if you guys know of a bug that should be |
8 |
addressed specifically in the gcc-4.3.0 ebuild, speak up now). |
9 |
|
10 |
then move on to the gcc 4.3 tracker bug (#198121). once this gets below a |
11 |
certain critical mass (i wont know what the critical mass is until it's been |
12 |
de-attained), then we'll be ~arching things. people are recommended to do a |
13 |
quick sweep of the lower hangers (many bugs have simple patches). |
14 |
|
15 |
i'll drop in ~ppc ~amd64 ~x86 as i use those every day. if any other arch is |
16 |
happy now with things, add your ~arch to the commented out list in cvs so i |
17 |
know to include it. |
18 |
-mike |