apenwarr-redo/t/clean.do

redo example/clean curse/clean
rm -f c c.c c.c.c c.c.c.b c.c.c.b.b d
rm -f hello [by]ellow *.o *~ .*~ CC LD
Add t/curse, a multi-level dependency build that really aggravates redo. ...because it seems my locking isn't very good. It exposes annoying problems involving rebuilding the same files more than once, screwing up stamp files with redo -j, and being unnecessarily slow when checking dependencies. So it's a pretty good test considering how simple it is. Didn't add it to t/all.do yet, because it would fail. 2010-11-19 00:28:16 -08:00			`redo example/clean curse/clean`
Support for default..do rules. I think* this was the last missing part from djb's spec. Certainly it's an important one for any real project. 2010-11-16 01:59:32 -08:00			`rm -f c c.c c.c.c c.c.c.b c.c.c.b.b d`
A whole bunch of cleanups to state.Lock. Now t/curse passes again when parallelized (except for the countall mismatch, since we haven't fixed the source of that problem yet). At least it's consistent now. There's a bunch of stuff rearranged in here, but the actual important problem was that we were doing unlink() on the lock fifo even if ENXIO, which meant a reader could connect in between ENXIO and unlink(), and thus never get notified of the disconnection. This would cause the build to randomly freeze. 2010-11-19 06:04:45 -08:00			`rm -f hello [by]ellow .o ~ .*~ CC LD`