*** Greg Reagle [2020-12-18 07:37]:
>redo-c does *not* capture standard output by default.
You are right. So yes, of course I had to export REDO_STDOUT=1 before,
to make redo-c behaviour the same as DJB suggested.
--
Sergey Matveev (http://www.stargrave.org/)
OpenPGP: CF60 E89A 5923 1E76 E263 6
Thanks very much for you comprehensive and thorough reply. I'll be studying it
over the course of many days. I disagree with your first point though, so read
on.
On Fri, Dec 18, 2020, at 05:08, Sergey Matveev wrote:
> Just a remark: when using "basic" features of redo, just what DJB
> describe
*** Sergey Matveev [2020-12-17 21:44]:
>Now there are pure C https://github.com/leahneukirchen/redo-c
And by the way, it is less than 1kLOC even with completely built-in
SHA256 implementation and no dependencies. Supporint all necessary
redo-ifchange/ifcreate/always commands, jobserver (parallel b
*** Greg Reagle [2020-12-17 14:39]:
>Makefile implemented in apenwarr redo
Just a remark: when using "basic" features of redo, just what DJB
described, there is no difference between various redo implementations.
I used apenwarr/redo, apenwarr/do, redo-c and goredo with the same
project, with the
