There's not much in the way of DJB's documentation other than a conceptual sketch so there's much
room for interpretation.
There are many differences between the two implementations, some quite fundamental. redux uses sha1 checksums instead of timestamps. Timestamps cause all sorts of problems as we know from make.
apenwarr redo has all sorts of extra utilities to ameliorate the problems.
redux has the minimum functionality needed for the task (init, redo, redo-ifchange, redo-ifcreate)
and I don't think it needs any others.
Redux passes most apenwarr tests. The few it does not pass are apenwarr specific.
I've not tried the converse. Might be interesting.
I actually have a task list to add an apenwarr compatibility mode to redux so users can switch easily. At that point, it should pass all the apenwarr tests.
There are many differences between the two implementations, some quite fundamental. redux uses sha1 checksums instead of timestamps. Timestamps cause all sorts of problems as we know from make. apenwarr redo has all sorts of extra utilities to ameliorate the problems. redux has the minimum functionality needed for the task (init, redo, redo-ifchange, redo-ifcreate) and I don't think it needs any others.
Redux passes most apenwarr tests. The few it does not pass are apenwarr specific. I've not tried the converse. Might be interesting.
I actually have a task list to add an apenwarr compatibility mode to redux so users can switch easily. At that point, it should pass all the apenwarr tests.
Of course, redux is quite a bit faster too.