Am Samstag, 27. Februar 2010 19:01:32 schrieb Dan McGee:
As far as other changes, the package loop rework patch is the most important one. Rather than inefficiently unzip every package to get the .PKGINFO file and determine its name and version, we use the .db.tar.gz directly which saves us a ton of work in most cases.
Do you think this script should lock the repo while reading it's content? Otherwise there is a chance it reads a package or db file while it's being modified. We might even loose all previous data which would cause the script to reread all packages on the next run. The problem with all this might be that we end up with a bunch of scripts and operations which block each other. ATM, if we move a lot of packages, db-move will lock and unlock the repo for each of them. If one of our cronjobs gets lucky and catches the lock between two packages the move script will fail and we'll end up with an inconsistent repo. I guess one step to solve this is this (hard to read) patch http://code.phraktured.net/cgit.cgi/dbscripts/commit/?h=working&id=bfaec9eb47c1fe042b83f9539f81dca1cad609a2 And maybe we should even have read and write locks. -- Pierre Schmitz, https://users.archlinux.de/~pierre