A single Redofile kind of doesn't work with the hole concept of redo, sadly. However, most .do files will sit in some kind of out/ directory anyway, so I don't

A single Redofile kind of doesn't work with the hole concept of redo, sadly. However, most .do files will sit in some kind of out/ directory anyway, so I don't think that'd be a real issue in practise. Speaking of performance, apenwarrs redo implementation suffers mostly from excessive forking of the python runtime. Sake doesn't need to do this, but it needs to do more work at the start, so my guess would be that Sake is faster for any bigger project. That is assuming sequential builds though, because it seems like Sake doesn't support parallel building? EDIT: I believe you can create a fake "Redofile" even in apenwarr redo by just naming it "default.do" and switching on $1 to see what you are supposed to build. I even used this myself[0], but it's a hack, and should be replaced by something better. [0] https://github.com/Tharre/redo/blob/master/default.do https://github.com/Tharre/redo/blob/master/default.do