| 1 |
Hello, |
| 2 |
Right now I'm looking at more and more requests from users about being |
| 3 |
able to upgrade existing systems. |
| 4 |
|
| 5 |
currently we have two bug id's that seem "good" |
| 6 |
|
| 7 |
http://bugs.gentoo.org/show_bug.cgi?id=6553 |
| 8 |
http://bugs.gentoo.org/show_bug.cgi?id=5667 |
| 9 |
|
| 10 |
|
| 11 |
|
| 12 |
I also got a suggestion on IRC from Nazgul that we document some form of |
| 13 |
update process and place on the ISO as well... so heres the suggestion. |
| 14 |
|
| 15 |
Given a check by somone who's more intimate with the system I suggest we |
| 16 |
place "update-1.2-to-1.4.sh" in the portage/scripts dir (including a |
| 17 |
warning and the click-through to continue perhaps??) |
| 18 |
|
| 19 |
|
| 20 |
and, to place on the boot-cd, the rmerge script. |
| 21 |
|
| 22 |
The update would be a rather harsh "rebuild everything" operation, that |
| 23 |
will quite likely fail in many cases. |
| 24 |
|
| 25 |
either that, or we make the update-1.2-to-1.4.sh take a second step and |
| 26 |
find + check all libstdc++ links and rebuild those packages... this |
| 27 |
would make it a simpler, albeit technically more bothersome, update. |
| 28 |
|
| 29 |
|
| 30 |
could anyone with time+knowledge please step up and help out with such a |
| 31 |
script? |
| 32 |
|
| 33 |
|
| 34 |
//Spider |
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
|
| 39 |
-- |
| 40 |
begin .signature |
| 41 |
This is a .signature virus! Please copy me into your .signature! |
| 42 |
See Microsoft KB Article Q265230 for more information. |
| 43 |
end |
Archives