From: Roman Zilka <zilka@fi.muni.cz>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] python-2.7 && python-updater
Date: Mon, 28 Mar 2011 17:41:40 +0200 [thread overview]
Message-ID: <20110328174140.df27208d.zilka@fi.muni.cz> (raw)
In-Reply-To: <4D908BAF.2090900@konstantinhansen.de>
KH (Mon, 28 Mar 2011 15:22:55 +0200):
> I do have python-2.7 and python-3.1 emerged. I just took al look in
> /usr/lib64/ and I can find trace of python2.4 python2.5 python2.6
> python2.7 python3.1 . Are those folders (2.4; 2.5; 2.6) needed anymore?
> If no, why are the still there?
Is there anything else inside those dirs besides *.pyc and *.pyo files?
If not, it's safe to remove them. *.py[co] are pre-semi-compiled python
programs that python creates upon the first run of a *.py source. Some
1-2 years ago (and before) portage couldn't handle these remnants, as
they didn't actually belong to any package. So if you had unmerged a
package containing a python program which had been run at least once
before the unmerge, the *.py[co] files were left in otherwise empty
directories. Python-2.4 and 2.5 may fall into this period of history.
2.6 is odd.
If the directories contain something more than *.py[co], the story is
different. If there are no files that belong to any package, I believe
it's safe to remove them. If something in there does belong to an
installed package, a re-emerge should solve the problem. If you need an
elegant way of sorting out the chaff, refer to a recent thread on this
mailinglist - "How can I find all "orphaned" files?".
-rz
next prev parent reply other threads:[~2011-03-28 15:43 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 0:11 [gentoo-user] python-2.7 && python-updater Mark Knecht
2011-03-25 0:28 ` Dale
2011-03-25 3:42 ` Amankwah
2011-03-25 4:48 ` Paul Hartman
2011-03-25 9:37 ` Dale
2011-03-25 9:50 ` Neil Bothwick
2011-03-25 13:56 ` Mark Knecht
2011-03-25 14:26 ` Neil Bothwick
2011-03-25 18:14 ` [gentoo-user] humor: " James
2011-03-25 14:33 ` [gentoo-user] " Roman Zilka
2011-03-25 16:44 ` Dale
2011-03-25 14:33 ` Paul Hartman
2011-03-25 16:46 ` Dale
2011-03-28 13:22 ` KH
2011-03-28 15:02 ` Mark Knecht
2011-03-28 15:41 ` Roman Zilka [this message]
2011-03-29 8:26 ` KH
2011-03-25 13:02 ` [gentoo-user] " Simon Siemonsma
2011-03-25 16:50 ` Dale
2011-03-25 19:09 ` [gentoo-user] " Stéphane Guedon
2011-03-25 19:21 ` Grant
2011-03-25 20:38 ` Neil Bothwick
2011-03-26 19:10 ` Mark Knecht
2011-03-26 19:22 ` Mick
2011-03-26 19:56 ` Mark Knecht
2011-03-26 20:36 ` Bill Longman
2011-03-26 20:53 ` Mark Knecht
2011-03-26 21:12 ` Mick
2011-03-26 21:16 ` Neil Bothwick
2011-03-26 21:33 ` Mark Knecht
2011-03-26 23:06 ` Adam Carter
2011-03-27 0:44 ` Neil Bothwick
2011-03-27 15:26 ` Mark Knecht
2011-03-27 15:47 ` Jacques Montier
2011-03-27 19:25 ` Neil Bothwick
2011-03-27 19:50 ` Mark Knecht
2011-03-27 20:05 ` Neil Bothwick
2011-03-28 0:45 ` Adam Carter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110328174140.df27208d.zilka@fi.muni.cz \
--to=zilka@fi.muni.cz \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox