| 1 |
Yes, it would be good to have an entry in the kbase with an overall |
| 2 |
description of what has to be done in order to properly update the |
| 3 |
toolchain. |
| 4 |
|
| 5 |
A link to the GCC Upgrade Guide (and to any other guide with further |
| 6 |
information) may appear where it's needed, since the kbase is supposed |
| 7 |
to give concise instructions only. Of course, all this method should be |
| 8 |
agreed between developers before. |
| 9 |
|
| 10 |
But as you said, IMO, maybe you should keep these ideas for a maturer |
| 11 |
stage of kbase's development. |
| 12 |
|
| 13 |
-- |
| 14 |
Pablo Antonio (AKA crazy2k) |
| 15 |
http://www.pablo-a.com.ar/ |
| 16 |
|
| 17 |
-- |
| 18 |
gentoo-kbase@g.o mailing list |
Archives