On Fri, Dec 24, 2010 at 11:58:00AM -0800, Vagrant Cascadian wrote: > in theory, should approx currently handle if: > > 1. machine A downloads pdiffs from yesterday > 2. approx applies them sucessfully > 3. time passes and the Packages file approx cached gets out of date > 4. machine B needs to downloads pdiffs from the last 3 days > > does approx deny machine B the Packages.diff/Index, even though approx doesn't > have a current Packages file? how does machine B end up a current Packages > file?
Ah, you're right. Approx will only deny the DiffIndex if it has an up-to-date Packages file. So in this case the client will indeed do some extra work downloading pdiffs and applying them. I'll look into how to cache the pdiffs for a future release (the caching itself is easy, the main impact will be on the GC and update code). BTW, you can have approx always deny pdiffs by setting $pdiffs to false in the config -- this is often the best choice when you have a fast network connection. -- Eric Cooper e c c @ c m u . e d u -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
