On Wed, Sep 26, 2001 at 11:01:05PM -0600, Jason Gunthorpe wrote: > It wouldn't be a cache so much as an active partial mirror, who's content > is driven by client requests. So if I fetch foo.deb one day, the 'cache' > would fetch all future versions of foo.deb and all its' dependencies > recursively in anticipation that I would eventually upgrade foo.deb > > Some people might want some code to make the cache bounded in size though. > > > - Priming the cache before running upgrades (wget --delete-after) > > That only works for 1 workstation. You really need to aggregate package > selections for all workstations and manage the cache that way.
This still sounds like a client-side app to me. Aggregate package selections, build a list of all installed packages, cross-reference that with an up-to-date available packages list to resolve dependencies and find URLs, and download everything through a standard-issue caching proxy server. -- - mdz
