Re: identifying unused manually installed packages

2014-03-28 Thread Sven Bartscher
On Fri, 28 Mar 2014 09:05:49 +0800 Paul Wise wrote: > On Fri, Mar 28, 2014 at 5:36 AM, Sven Bartscher wrote: > > > Also I'm not really sure if this is even a good idea, or if there is > > maybe another program already present which does already identify > > unused, manually installed packages an

Re: identifying unused manually installed packages

2014-03-27 Thread Paul Wise
On Fri, Mar 28, 2014 at 5:36 AM, Sven Bartscher wrote: > Also I'm not really sure if this is even a good idea, or if there is > maybe another program already present which does already identify > unused, manually installed packages and I just didn't find it. deborphan seems like a similar package

Re: identifying unused manually installed packages

2014-03-27 Thread Don Armstrong
On Thu, 27 Mar 2014, Sven Bartscher wrote: > This approach also brings some problems. For example some packages > that have files which belong to a frequently scanned database aren't > detected because they are accessed by the scan. popcon-largest-unused gets at this somewhat, and you could achiev

Re: identifying unused manually installed packages

2014-03-27 Thread Russ Allbery
Sven Bartscher writes: > I thought a little while about this problem and came up with the idea, > that every manually installed package whose files were not accessed for > more than a specified time (a month, a year, whatever) could be > considered unneeded. > So I started writing a script that

identifying unused manually installed packages

2014-03-27 Thread Sven Bartscher
Greetings everyone. As we all know apt-get does a very good job, by identifying which packages were installed automatically as dependencies and aren't needed anymore. Wile this is very nice, I still fear that, from time to time, there are manually installed packages gathering on my computer which I