Hello Eduard, On Sun, Jul 17, 2011 at 11:45:47AM +0200, Eduard Bloch wrote: > #include <hallo.h> > * Helge Kreutzmann [Sun, Jul 17 2011, 10:45:19AM]: > In fact, it deletes them after X days after they became > no longer downloadable. As long as the index files (like Packages.*) are > good and can be checked by download lookups, the files referenced > therein will stay in the cache.
Thanks for your explanation.
> The potential pitfall in this scheme is the renaming of stable
> to oldstable. If nobody ever downloaded from oldstable then the server
> won't know about it. But when it was used once before or within the
> grace period then the problem will naturally disappear.
>
> Now, does this provide a sufficient solution to your needs or do we
> still need version based tracking?
apt-proxy worked differently. Once a new version of a package was
downloaded, the proxy would check if there are more than N versions
already in the cache (e.g. N=4). If yes, then the lowest version was
removed (if it was the fith version, say). If no, nothing happended.
This has (for me) two advantages: First, if something breaks, I always
have the N latest version in the cache and can go back (or check if it
is already present in the older version) and b) if some package gets
removed from Debian, then it still remains in the cache.
Of course, these are the *added* use cases, beside the caching aspect.
After filing the bug I checked if other package proxies/caches
implemented such a scheme, but it seems this was a unique feature of
apt-proxy which was removed from Debian. Therefore if such a scheme would
become possible with apt-cacher-ng, this would be great. Otherwise I
perfectly understand if this is a use case you / your upstream
considers not worth pursuing.
Greetings
Helge
--
Dr. Helge Kreutzmann [email protected]
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: Digital signature
