apenwarr-redo/minimal
Avery Pennarun ec72beb343 minimal/do: don't create a .did file until after a file is actually built.
With the new "continue" feature on by default, it turned out that
ctrl-c during a build, or a .do file returning an error, would mark a
target as "built" even though it hadn't been.  This would prevent
retrying it when you started minimal/do again.  Use a temp file
instead.

It's a little tricky: to prevent accidental recursion, we want to
create a file *before* building, but clean up that file when starting
the next session.  And we rename that file to the actual .did file
*after* building successfully.
2018-11-02 04:25:35 -04:00
..
fakedir minimal/do: add redo-whichdo support and internal unit tests. 2018-11-02 02:20:52 -04:00
default.zz.do minimal/do: add redo-whichdo support and internal unit tests. 2018-11-02 02:20:52 -04:00
do minimal/do: don't create a .did file until after a file is actually built. 2018-11-02 04:25:35 -04:00
do.test minimal/do: add redo-whichdo support and internal unit tests. 2018-11-02 02:20:52 -04:00
test.do minimal/do: add redo-whichdo support and internal unit tests. 2018-11-02 02:20:52 -04:00