From: Mike Kazantsev <mk.fraggod@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Finding orphaned libs
Date: Tue, 9 Jun 2009 19:01:11 +0600 [thread overview]
Message-ID: <20090609190111.354f05a1@coercion> (raw)
In-Reply-To: <4A2DAC7B.6060806@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
On Mon, 08 Jun 2009 19:27:39 -0500
Dale <rdalek1967@gmail.com> wrote:
> > Also, be careful when you parse the output of the command. Most of the
> > .pyc and .pyo files in the python2.5 directories are byte-compiled
> > version that python generated dynamically the first time they are
> > used. For example: ..../Numeric/numeric_version.py was installed by
> > the ebuild and thuse qfile tells me it belongs to dev-python/numeric,
> > but .../Numeric/numeric_version.pyc is listed as an "orphan". While it
> > is safe to delete, it will just be regenerated again later, wasting
> > computing cycles.
>
> That's sort of what I was thinking. It was generated when it was
> started up the first time. I also noticed some things that I installed
> in the Seamonkey directory too. Adblock was one of those.
That's not quite correct: .py[co] are generated by emerge right after
package installaton and these won't come back unless you use these libs
as root, since python won't have write access to these paths and will
be byte-compiling each script on-the-fly.
--
Mike Kazantsev // fraggod.net
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-06-09 13:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 20:44 [gentoo-user] Finding orphaned libs Alan McKinnon
2009-06-08 20:54 ` Neil Bothwick
2009-06-08 22:10 ` Alan McKinnon
2009-06-08 22:57 ` Dale
2009-06-08 23:31 ` Willie Wong
2009-06-09 10:05 ` Joerg Schilling
2009-06-09 10:54 ` Neil Bothwick
2009-06-08 23:52 ` Dale
2009-06-09 0:18 ` Willie Wong
2009-06-09 0:27 ` Dale
2009-06-09 7:03 ` Alan McKinnon
2009-06-09 13:01 ` Mike Kazantsev [this message]
2009-06-10 7:53 ` Dale
2009-06-10 8:37 ` Mike Kazantsev
2009-06-09 13:33 ` Volker Armin Hemmann
2009-06-09 13:48 ` Joerg Schilling
2009-06-09 14:04 ` Volker Armin Hemmann
2009-06-09 14:34 ` Neil Bothwick
2009-06-09 14:51 ` Joerg Schilling
2009-06-09 14:08 ` Mickaël Bucas
2009-06-09 14:15 ` Joerg Schilling
2009-06-09 14:36 ` Neil Bothwick
2009-06-09 14:42 ` Paul Hartman
2009-06-09 14:52 ` Neil Bothwick
2009-06-09 14:59 ` Joerg Schilling
2009-06-09 15:29 ` Neil Bothwick
2009-06-09 15:21 ` Etaoin Shrdlu
2009-06-09 15:28 ` Neil Bothwick
2009-06-09 15:20 ` Etaoin Shrdlu
2009-06-09 15:30 ` Alan McKinnon
2009-06-09 14:39 ` Mickaël Bucas
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=20090609190111.354f05a1@coercion \
--to=mk.fraggod@gmail.com \
--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