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.
This commit is contained in:
parent
25d24d117f
commit
ec72beb343
11 changed files with 39 additions and 21 deletions
4
.gitignore
vendored
4
.gitignore
vendored
|
|
@ -1,8 +1,8 @@
|
|||
/.redo
|
||||
/.do_built
|
||||
/.do_built.dir
|
||||
*~
|
||||
*.pyc
|
||||
*.tmp
|
||||
/redo-sh
|
||||
*.did
|
||||
.do_built
|
||||
.do_built.dir
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue