Re: Finding left-over libraries

["Gary Hennigan" <glhenni@sandia.gov>]

peter karlsson <pk@mds.mdh.se> writes:
> Brian Servis:
> 
> > Unforunately there is no way to do this cleanly now.  
> 
> That's too bad.
> 
> > One of the issues to be concerned with is on a machine used for
> > development where nothing directly depends on a lib*-dev package except at
> > build time when you need to link to the headers.
> 
> Yeah, well, all I want is a *report* on what is installed that nothing
> depends on. I don't want it to automatically purge everything for me...
> 
> > There is a Debian package called cruft that can do some system searching
> > and can give you a very rough idea of file usage. 
> 
> I couldn't get it to work.

I believe the current version in potato is broken (take a look at the
bug reports for it). However, I used it on my slink system some time
ago and it is very helpful in finding files and such on your system
that aren't associated with a package, but I don't believe it'll find
packages without dependents, at least from reading the documentation,
and using my poor memory, I don't get that impression.

I do agree with you, it'd be nice to have such a utility.

Gary