| View previous topic :: View next topic |
| Author |
Message |
leej
Apprentice
Joined: 18 May 2002
Posts: 280
|
 Posted: Thu Jun 06, 2002 11:34 pm Post subject: Python unmerged - bye bye portage - *whooops*! ;-) |
 |
|
I erm <blush> unmerged (cleaned) python when told to recompile it against tcltk, thereby breaking emerge.
To fix it, I've extracted the stage 1 tarball and copied /usr/lib/python2.2 and /usr/include/python2.2 over to my /root partition. Then all files that began with python* over /usr/bin (and I think one to /usr/sbin). And that allowed me to reemerge python.
Have I done this right? Also, will there be any stray files left over or will portage clean them up the next time I do a clean? I'm a bit Monica Geller about having a tidy hard disk!  |
|
| Back to top |
|
 |
BradN
Advocate
Joined: 19 Apr 2002
Posts: 2391
Location: Wisconsin (USA)
|
| Posted: Fri Jun 07, 2002 12:34 am Post subject: |
|
|
| I don't think it should leave anything dangerous around as long as you've sucessfully re-emerged python after it - that should replace any still in use files. I'd probably think all the files have been replaced, but it's always possible there could be an old file or two... I wouldn't worry about it. |
|
| Back to top |
|
|
leej
Apprentice
Joined: 18 May 2002
Posts: 280
|
| Posted: Fri Jun 07, 2002 12:41 am Post subject: |
|
|
Thanks Brad. The only problem I've had since posting is not being able to do a
However, re-emering portage solved that problem. I just hope I didn't break anything else. 
I thought I'd post that bit of extra info about portage in case anybody else does the same and does a search here. I notice somebody else on these forums accidentally unmerged python but the info provided is very minimal and refers back to the mailing list. |
|
| Back to top |
|
|
|
Portage & Programming
