> could it be that cvs-level locking provides a nice filesystem-based sync?
The various threads all do CVS or SVN into completely separate (peer) directories, so there really ought be no overlap at that point. The 'worklist' (where to get chores from) is synchronized [using Java term] with a lock. The only real prospect for problems (right now) are (1) if a module update fails and the code try to 'propagate the failure state' to dependees (straying into other modules in the tree, that could be updated & changing state) and (2) moving the module from the "to-do" to the "done" lists on the run (the largest risk, IMHO) and pretty easy to fix. We probably need to make 'state propagation across the dependency tree' synchronized, so we can do multi-threaded builds, but that is a little trickier to do. A brute force 'run lock' might be fine for this. regards, Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
