public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Willie Wong <wwong@math.princeton.edu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Finding orphaned libs
Date: Mon, 8 Jun 2009 19:31:22 -0400	[thread overview]
Message-ID: <20090608233122.GA30512@princeton.edu> (raw)
In-Reply-To: <20090608215408.3c4b4c91@krikkit.digimed.co.uk>

On Mon, Jun 08, 2009 at 09:54:08PM +0100, Penguin Lover Neil Bothwick squawked:
> On Mon, 8 Jun 2009 22:44:18 +0200, Alan McKinnon wrote:
> 
> > Is there an easy way to detect the orphaned libs on and old machine
> > who's install dates back to 2004? The only idea I can come up with is 
> > 
> > for I in /usr/lib/*.so.* ; do equery belongs $I ; done
> 
> qfile --orphans /usr/lib/*.so.*
> 
> or, maybe cleaner
> 
> qfile --orphans $(find -H /usr/lib /lib -type f)
> 
> which avoids checking all the symlinks.
> 
> Then run symlinks remove any dangling links left over.

Whoa, that's useful. Thanks for Neil for giving the solution, and to
Alan for even asking the question. Having a box whose install dates to 

sep~ # head /var/log/emerge.log
Started emerge on: Nov 03, 2002
 *** emerge  >=sys-apps/baselayout-1.7.9-r1 >=sys-apps/texinfo-4.2-r1 sys-devel/gettext >=sys-devel/binutils-2.13.90.0.4 >=sys-devel/gcc-3.2
>>> emerge (1 of 7) sys-apps/baselayout-1.8.4.1 to /
::: completed emerge (1 of 7) sys-apps/baselayout-1.8.4.1 to /
>>> emerge (2 of 7) sys-apps/texinfo-4.2-r5 to /

This seems to be a worthy enterprise. 

BTW, though, $(find -H ...) will have too big a list. Perhaps better
to do 

find -H /usr/lib /lib -type f | xargs qfile -o

W
-- 
When my cats aren't happy, I'm not happy. Not because I care about their mood 
but because I know they're just sitting there thinking up ways to get even.
    ~Penny Ward Moser
Sortir en Pantoufles: up 913 days, 22:12



  parent reply	other threads:[~2009-06-08 23:28 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 [this message]
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
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=20090608233122.GA30512@princeton.edu \
    --to=wwong@math.princeton.edu \
    --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