| 1 |
On Sat, Jul 26, 2008 at 4:20 PM, Nikos Chantziaras <realnc@×××××.de> wrote: |
| 2 |
> Dale wrote: |
| 3 |
>> |
| 4 |
>> Mark Knecht wrote: |
| 5 |
>>> |
| 6 |
>>> As part of emerge -DuN system portage appears to first make me remove |
| 7 |
>>> python by hand. Is this safe? |
| 8 |
>> |
| 9 |
>> No! Not until you get a working version installed. Portage needs python. |
| 10 |
>> Someone correct me if I misstep here: |
| 11 |
>> |
| 12 |
>> emerge the new python, run the python updater and let it emerge whatever |
| 13 |
>> packages it needs to rebuild, check to make sure nothing still needs the old |
| 14 |
>> version and then you can unmerge the old one. |
| 15 |
>> |
| 16 |
>> I think that is the correct way. |
| 17 |
> |
| 18 |
> It is. *Only* unmerge the old Python after you emerged the new one *and* |
| 19 |
> ran python-updater. |
| 20 |
> |
| 21 |
> Unmerging Python without first emerging the new version is equivalent to |
| 22 |
> sawing off the branch you are sitting on. You could as well unmerge portage |
| 23 |
> itself and wonder where portage went and why you can't emerge. |
| 24 |
> |
| 25 |
|
| 26 |
Thanks. That is sort of what I thought but I felt it best to ask |
| 27 |
first. It seems I have python oriented things in my world file that |
| 28 |
I'm not clear need to be there. One is python-updater. I'll emerge |
| 29 |
python first and then return to look at how emerge -DuN world would |
| 30 |
proceed. |
| 31 |
|
| 32 |
Thanks! |
| 33 |
|
| 34 |
Cheers, |
| 35 |
Mark |
Archives