Date: Fri, 18 May 2007 15:47:27 +0100 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-ports@freebsd.org Subject: Re: Specs for saving old shared libs Message-ID: <20070518154727.019d3c31@gumby.homeunix.com.> In-Reply-To: <17997.40528.630013.491475@jerusalem.litteratus.org> References: <20070507184231.GA50639@xor.obsecurity.org> <1179437517.8912.5.camel@ikaros.oook.cz> <20070518075058.GB1164@turion.vk2pj.dyndns.org> <200705181409.15561.mail@maxlor.com> <17997.40528.630013.491475@jerusalem.litteratus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 18 May 2007 08:38:40 -0400 Robert Huff <roberthuff@rcn.com> wrote: > Benjamin Lutz writes: > > > The last part seems to be the catch here. How about providing a > > tool that scans all binaries in the standard locations for what > > libs they depend on, and also allows the user/admin to specify > > the paths to binaries that he installed on his own, then outputs > > a list of unused libraries? > > Are you aware of "libchk" and "portsclean"? > I have dozens of these libraries in my compat/pkg directory and I doubt that any should be needed, since I'm fully up-to-date, and mostly use portmanager. And yet portsclean never touches them, so I'm guessing that it only actually removes obsolete libraries that are shadowed by installed libraries. One thing that does worry me a bit, is the possibility that a new port install might find these one of these orphaned libraries, and fail to install a LIB_DEPENDS port.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070518154727.019d3c31>