implemented. Why yet another implementation? It is feature full and has
better performance comparing to shell and Python implementation.
+It passes tests from dieweltistgarnichtso.net's redo-sh.tests and
+implementation-neutral from apenwarr/redo.
+
goredo is free software: see the file COPYING for copying conditions.
Home page: http://www.goredo.cypherpunks.ru/
INSTALL *goredo-install*
+
+Hopefully it should work on all POSIX systems.
>
$ go get go.cypherpunks.ru/goredo
$ goredo -symlinks
$ git clone git://git.cypherpunks.ru/goredo.git
$ cd goredo
- $ git tag -v v0.5.0
+ $ git tag -v v0.8.0
$ git clone git://git.cypherpunks.ru/gorecfile.git
- $ ( cd gorecfile ; git tag -v v0.3.0 )
+ $ ( cd gorecfile ; git tag -v v0.4.0 )
$ echo "replace go.cypherpunks.ru/recfile => `pwd`/gorecfile" >> go.mod
$ git clone git://git.cypherpunks.ru/gotai64n.git
$ ( cd gotai64n ; git tag -v v0.2.0 )
$REDO_TOP_DIR environment variable, or by having .redo/top file in it
* target's completion messages are written after they finish
* executable .do is run as is, non-executable is run with /bin/sh -e[x]
-* tracing (-x) can be done only for non-executable .do
+* tracing (-x) can be obviously done only for non-executable .do
+* parallizable build is done only during redo-ifchange for human
+ convenience: you can globally enable REDO_JOBS, but still do for
+ example: redo htmls infos index upload
FEATURES *goredo-features*