| 1 |
On 2008-07-26, Dale <dalek1967@×××××××××.net> wrote: |
| 2 |
|
| 3 |
> emerge the new python, run the python updater and let it emerge whatever |
| 4 |
> packages it needs to rebuild, check to make sure nothing still needs the |
| 5 |
> old version and then you can unmerge the old one. |
| 6 |
|
| 7 |
Be warned: running python-updater can take a long time (as in a |
| 8 |
day or more) on older machines. It rebuilds things like open |
| 9 |
office. |
| 10 |
|
| 11 |
> I think that is the correct way. |
| 12 |
> |
| 13 |
> It is also safer to keep a spare copy of some things around in case you |
| 14 |
> mess up to. man make-conf and look for buildsyspkg. |
| 15 |
|
| 16 |
If it were me, I'd leave the old Python around for while. |
| 17 |
There's no real reason you need to unmerge it (unless you're |
| 18 |
running out of disk space). |
| 19 |
|
| 20 |
-- |
| 21 |
Grant Edwards grante Yow! Catsup and Mustard |
| 22 |
at all over the place! It's |
| 23 |
visi.com the Human Hamburger! |
Archives