man deborphan
man cruft
Just how accurate are these two utilities at identifying unneccessary items on your system? Running deborphan on my system (Karmic KDE 4.4.1) reports:
deborphan --guess-data identifies one additional item:
deborphan --guess-all identifies:
I then ran cruft wih the -r option (output to a file) and the results are significant.
I like having a 'clean' system, one that doesn't have bits and pieces of leftover, un-needed 'junk.' So, can I 'trust' the results of these two utilities?
DESCRIPTION
deborphan finds packages that have no packages depending on them. The
default operation is to search only within the libs and oldlibs sec‐
tions to hunt down unused libraries.
If it is invoked with an optional list of packages, only the dependen‐
cies on those packages will be checked. The results are printed to std‐
out as if the option --show-deps had been given. Searching for specific
packages will show the package, regardless of its priority. It is pos‐
sible to specify -, to read a list of packages from standard input.
deborphan finds packages that have no packages depending on them. The
default operation is to search only within the libs and oldlibs sec‐
tions to hunt down unused libraries.
If it is invoked with an optional list of packages, only the dependen‐
cies on those packages will be checked. The results are printed to std‐
out as if the option --show-deps had been given. Searching for specific
packages will show the package, regardless of its priority. It is pos‐
sible to specify -, to read a list of packages from standard input.
DESCRIPTION
This manual page documents briefly the cruft command. Please see
/usr/share/doc/cruft/README.gz for more information.
cruft is a program that goes over the Debian packaging system's data‐
base, and compares the contents of that with the files actually on your
system, and produces a summary of the differences.
This manual page documents briefly the cruft command. Please see
/usr/share/doc/cruft/README.gz for more information.
cruft is a program that goes over the Debian packaging system's data‐
base, and compares the contents of that with the files actually on your
system, and produces a summary of the differences.
w32codecs
libkexiv2-7
libavcodec-unstripped-52
libdns50
libsnmp15
libscim8c2a
libk3b6-extracodecs
libtunepimp5-mp3
libstrigiqtdbusclient0
soprano-backend-sesame
libkexiv2-7
libavcodec-unstripped-52
libdns50
libsnmp15
libscim8c2a
libk3b6-extracodecs
libtunepimp5-mp3
libstrigiqtdbusclient0
soprano-backend-sesame
hplip-data
amarok-dbg
w32codecs
libkexiv2-7
libkorundum4-ruby1.8
libavcodec-unstripped-52
python-sip4
kdebase-runtime-data-common
kdebase-runtime-bin-kde4
libdns50
libsnmp15
libscim8c2a
libk3b6-extracodecs
libtunepimp5-mp3
libstrigiqtdbusclient0
python-imaging
hplip-data
soprano-backend-sesame
w32codecs
libkexiv2-7
libkorundum4-ruby1.8
libavcodec-unstripped-52
python-sip4
kdebase-runtime-data-common
kdebase-runtime-bin-kde4
libdns50
libsnmp15
libscim8c2a
libk3b6-extracodecs
libtunepimp5-mp3
libstrigiqtdbusclient0
python-imaging
hplip-data
soprano-backend-sesame
I like having a 'clean' system, one that doesn't have bits and pieces of leftover, un-needed 'junk.' So, can I 'trust' the results of these two utilities?
Comment