On Fri, Aug 29, 2008 at 03:52:42PM -0700, Dominique Brazziel wrote: > feta status gcc-4.1-base gcc-4.2-base > > Running: dpkg --status 'gcc-4.1-base' 'gcc-4.2-base' > Package: gcc-4.1-base > Status: purge ok not-installed > Priority: optional > Section: libs > > Package: gcc-4.2-base > Status: purge ok not-installed > Priority: required > Section: libs > > ls -l gcc-4.*-base* > -rw-r--r-- 1 root root 207522 2008-06-24 09:32 gcc-4.1-base_4.1.2-23_i386.deb > -rw-r--r-- 1 root root 98764 2008-07-05 19:32 gcc-4.2-base_4.2.4-3_i386.deb > -rw-r--r-- 1 root root 102636 2008-08-14 17:17 gcc-4.3-base_4.3.1-9_i386.deb >
You are still misunderstanding this. Even though the files are no longer installed on the system, they are still part of the distribution and therefore are kept in apt-cacher's cache. They are only removed from there once they are removed from the distribution. This is in case another machine on your network wants to install them. Then you have saved bandwidth by only downloading the files once. It is nothing to do with what is currently installed on particular machine(s). Apt-cacher is a proxy cache for a group of machines to save having to download the same file multiple times for each machine. Do you have multiple machines on a network? If not, apt-cacher is probably of no use to you. Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
