implemented. Why yet another implementation? It is feature full and has
better performance comparing to shell and Python implementation.
implemented. Why yet another implementation? It is feature full and has
better performance comparing to shell and Python implementation.
goredo is free software: see the file COPYING for copying conditions.
Home page: http://www.goredo.cypherpunks.ru/
INSTALL *goredo-install*
goredo is free software: see the file COPYING for copying conditions.
Home page: http://www.goredo.cypherpunks.ru/
INSTALL *goredo-install*
authenticity of go.cypherpunks.ru TLS connection, then you can disable
their usage by setting GOPRIVATE=go.cypherpunks.ru. If you still have
problems with the authenticity on your side, then build it manually: >
$ git clone git://git.cypherpunks.ru/goredo.git
$ cd goredo
authenticity of go.cypherpunks.ru TLS connection, then you can disable
their usage by setting GOPRIVATE=go.cypherpunks.ru. If you still have
problems with the authenticity on your side, then build it manually: >
$ git clone git://git.cypherpunks.ru/goredo.git
$ cd goredo
$ 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 )
$ 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 )
* "all" target is default
* stdout is always captured, but no target is created if it was empty
* empty targets are considered always out of date
* "all" target is default
* stdout is always captured, but no target is created if it was empty
* empty targets are considered always out of date
* .do search goes up to / by default, but can be limited with either
$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]
* .do search goes up to / by default, but can be limited with either
$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
* redo-dot -- dependency DOT graph generator. For example to visualize
your dependencies with GraphViz: >
$ redo target [...] # to assure that **/.redo/*.dep are filled up
* redo-dot -- dependency DOT graph generator. For example to visualize
your dependencies with GraphViz: >
$ redo target [...] # to assure that **/.redo/*.dep are filled up
redo-stamp-ing its dependants won't be rebuilt further, but build time
will be already ruined. If you need to rebuild TeX documents (case
mentioned in redo-sh's FAQ) until all references and numbers are ready,
redo-stamp-ing its dependants won't be rebuilt further, but build time
will be already ruined. If you need to rebuild TeX documents (case
mentioned in redo-sh's FAQ) until all references and numbers are ready,
-then you must simply explicitly use while cycle in your .do, as
-apenwarr/redo already suggests.
+then you must naturally expectedly explicitly use while cycle in your
+.do, as apenwarr/redo already suggests.