From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Finding orphaned libs
Date: Mon, 08 Jun 2009 19:27:39 -0500 [thread overview]
Message-ID: <4A2DAC7B.6060806@gmail.com> (raw)
In-Reply-To: <20090609001816.GA28479@princeton.edu>
Willie Wong wrote:
> On Mon, Jun 08, 2009 at 06:52:23PM -0500, Penguin Lover Dale squawked:
>
>> Questions: You knew I subscribed to this list. lol I ran the command:
>>
>> find -H /usr/lib /lib -type f | xargs qfile -o
>>
>> and I got a lot of hits. I'm just going to post snippets of the
>> directories here. It is a LONG list otherwise.
>>
>> /usr/lib/gimp/2.0/plug-ins/
>> /usr/lib/perl5/site_perl/5.8.8/i486-linux/sys/
>> /usr/lib/python2.5/site-packages/dbus/
>> /usr/lib/python2.5/site-packages/Numeric/
>> /usr/lib/python2.5/site-packages/PyQt4/uic/
>> /usr/lib/python2.5/site-packages/Pyrex/Plex/
>> /usr/lib/portage/pym/
>>
>> Some of those directories have additional directories in them but I
>> tried to hit the highlights. Now to my questions. Can these be
>> deleted? Should one make certain these doesn't belong to some package
>> somewhere? Should I update my backups BEFORE deleting these? o_O
>>
>
> Depends if you do have those packages installed. Numeric is from
> dev-python/numeric, for example.
>
> 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.
>
> Ditto for some of the files in the perl directory.
>
> W
>
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.
Tho there was a good many of them, I suspect most all of them belongs to
something here. I may just leave well enough alone, may poke around a
little but nothing risky.
Thanks.
Dale
:-) :-)
next prev parent reply other threads:[~2009-06-09 0:27 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 [this message]
2009-06-09 7:03 ` Alan McKinnon
2009-06-09 13:01 ` Mike Kazantsev
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=4A2DAC7B.6060806@gmail.com \
--to=rdalek1967@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