#include <hallo.h> * Damián Viano [Wed, May 04 2005, 09:22:12PM]: > > > Maybe not on-the-fly checking, (since I think that is the hardest > > > thing) but adding a rutine after the download that checks the md5 and > > > > There is not much difference between on-the-fly checking and doing that > > after every download, and the problem is still access to the package > > data (note that this data needs to be maintained as well). The one > > Yeap, of course that accessing package data is *great* cost. My > suggestion come from a misbelief, sory about that.
As said, using sqlite and Packages/Sources tracking can work around this wihout deep impact on performance. I have just included some hooks for checks into my apt-cacher 0.9beta5 which you can get from http://people.debian.org/~blade/testing/. Later today I plan to write the sqlite code for this hooks and then we will see. My first quick-and-dirty test showed that database updates are not really costy (44k entries in 15s on 1.9ghz box for update, read: once a day after changes of Packages/Sources. Checksum retrieval is very fast). Regards, Eduard. -- Russian roulette for linux: [ $[ $RANDOM % 6 ] == 0 ] && rm -rf / || echo "Still breathing, eh?"
