1 |
KH (Mon, 28 Mar 2011 15:22:55 +0200): |
2 |
> I do have python-2.7 and python-3.1 emerged. I just took al look in |
3 |
> /usr/lib64/ and I can find trace of python2.4 python2.5 python2.6 |
4 |
> python2.7 python3.1 . Are those folders (2.4; 2.5; 2.6) needed anymore? |
5 |
> If no, why are the still there? |
6 |
|
7 |
Is there anything else inside those dirs besides *.pyc and *.pyo files? |
8 |
If not, it's safe to remove them. *.py[co] are pre-semi-compiled python |
9 |
programs that python creates upon the first run of a *.py source. Some |
10 |
1-2 years ago (and before) portage couldn't handle these remnants, as |
11 |
they didn't actually belong to any package. So if you had unmerged a |
12 |
package containing a python program which had been run at least once |
13 |
before the unmerge, the *.py[co] files were left in otherwise empty |
14 |
directories. Python-2.4 and 2.5 may fall into this period of history. |
15 |
2.6 is odd. |
16 |
|
17 |
If the directories contain something more than *.py[co], the story is |
18 |
different. If there are no files that belong to any package, I believe |
19 |
it's safe to remove them. If something in there does belong to an |
20 |
installed package, a re-emerge should solve the problem. If you need an |
21 |
elegant way of sorting out the chaff, refer to a recent thread on this |
22 |
mailinglist - "How can I find all "orphaned" files?". |
23 |
|
24 |
-rz |