[Omake] OMake locking

[Jared C. Davis]

Hi,

> This is not really about locking - the basic assumption of OMake is that
> it does the global dependency analysis on the whole project, so in
> general you can not really have more than one instance of OMake running
> on the same project, without loosing some of the reliability guarantees
> that OMake is designed to provide. Also, there is a global per-project
> "build state" database (.omakedb) that is not designed for parallel
> access. The locking is there just to remind you of this limitation.

I guess I don't see why OMake should need to lock its database during
the entire time that a rule is being executed.  If we just need the
lock to ensure consistency when dependency and job completion
information is being read or written, then couldn't we just lock the
database when it's time to read/write that info, and unlock it the
rest of the time?

Thanks,
   Jared

-- 
Jared C. Davis <jared at cs.utexas.edu>
3600 Greystone Drive #604
Austin, TX 78731
http://www.cs.utexas.edu/users/jared/