[EMAIL PROTECTED] (Andrew M. Bishop):
> Felix Karpfen <[EMAIL PROTECTED]> writes:
> If you decide that having a local cache of debian packages is useful
> (for example if you have more than one computer to install them on)
> then using WWWOFFLE to cache the files is a good idea.
I just didn't realize that we can use wwwoffle as package proxy !
I use apt-proxy version 2 (sarge) for this, and it would be interesting to
compare performance and cache management. ap2 uses twisted, but can be
configured to drop parallel downloading (better for serial lines), so it's
simple wget again, in the end.
There should be some advantages of a specialized proxy, though.
For example, you can configure how many versions to hold, and under what
circumstances delete the expired. And it's naturally to have the apt-proxy
cache in one partition adapted in FS and the expected inodes, et al.
The same applies for wwwoffle, but both functions unmerged would allow more
fine tuning, and both should be slightly faster in harddisk access.
It's also easy to export the package cache completely since it's in one place.
This katter would probably occur more rarely, though.
Perhaps one can 'fork' the wwwoffle cache physically somehow (like lvm) ?
Or maybe you xould implement a 'package protocol' on http/ftp directory level ?
;))
OTOH keeping things simple (less services, less configurations) always is a
good thing.
�
/\/
