@section Hashing and stamping
All targets are checksummed if target's @file{ctime} differs from the
-previous one, or @env{REDO_INODE_NO_TRUST} environment variable is set.
+previous one, or @env{$REDO_INODE_NO_TRUST} environment variable is set.
@command{apenwarr/redo} gives
@url{https://redo.readthedocs.io/en/latest/FAQImpl/#why-not-always-use-checksum-based-dependencies-instead-of-timestamps, many reasons}
why every time checksumming is bad, but in my opinion in practice all of
@item targets, dependency information and their directories are explicitly
synced (can be disabled, should work faster)
@item file's change is detected by comparing its size, @code{ctime} (if
- @env{REDO_INODE_NO_TRUST} environment variable is not set) and
+ @env{$REDO_INODE_NO_TRUST} environment variable is not set) and
@url{https://github.com/BLAKE3-team/BLAKE3, BLAKE3} hash
@item files creation is @code{umask}-friendly (unlike @code{mkstemp()}
used in @command{redo-c})
If you have problems with @code{*.golang.org}'s inability to verify
authenticity of @code{go.cypherpunks.ru} TLS connection, then you can
-disable their usage by setting @env{GOPRIVATE=go.cypherpunks.ru}. You
-can override CA certificate file path with @env{SSL_CERT_FILE} and
-@env{GIT_SSL_CAINFO} environment variables.
+disable their usage by setting @env{$GOPRIVATE=go.cypherpunks.ru}. You
+can override CA certificate file path with @env{$SSL_CERT_FILE} and
+@env{$GIT_SSL_CAINFO} environment variables.
You can obtain development source code with
@command{git clone git://git.cypherpunks.ru/goredo.git}
@table @command
@item bmake
-Pass @code{-j 1 -J X,Y} arguments through @env{MAKEFLAGS} variable.
+Pass @code{-j 1 -J X,Y} arguments through @env{$MAKEFLAGS} variable.
@item gmake
-Pass @code{--jobserver-auth=X,Y} arguments through @env{MAKEFLAGS} variable.
+Pass @code{--jobserver-auth=X,Y} arguments through @env{$MAKEFLAGS} variable.
@item none
-Pass @code{X,Y} arguments through @env{REDO_JS_FD} variable.
+Pass @code{X,Y} arguments through @env{$REDO_JS_FD} variable.
Used by default, if @env{$REDO_MAKE} is not set.
@end table
@section Release 1.7.0
@itemize
@item
- Optional compatibility (through @env{REDO_MAKE=@{bmake|gmake@}})
+ Optional compatibility (through @env{$REDO_MAKE=@{bmake|gmake@}})
with either NetBSD's bmake or GNU Make jobserver protocols, being
able to tightly integrate @command{goredo} with the @command{make}.
@end itemize
@section Release 1.4.0
@itemize
@item
- Fixed proper @option{-xx} and @env{REDO_TRACE} workability, that
+ Fixed proper @option{-xx} and @env{$REDO_TRACE} workability, that
previously was not applied to all targets.
@item
Simpler statusline cleaning function, does not leading to whitespace
@code{Size} is stored in the state, for faster OOD detection.
Previous @command{goredo} state files won't work.
@item
- Setting of @env{REDO_INODE_NO_TRUST} environment variable brings no
+ Setting of @env{$REDO_INODE_NO_TRUST} environment variable brings no
trust to file inode's information (except for its size), forcing its
checksum checking.
@item
@section Release 0.12.1
@itemize
@item
- Tarball uses @file{vendor} directory without @env{GOPATH}
+ Tarball uses @file{vendor} directory without @env{$GOPATH}
overriding. @command{goredo} and its dependencies anyway uses Go
1.12+ versions, that have @file{vendor}-ing support.
@end itemize
@section Release 0.11.0
@itemize
@item
- Previously @env{REDO_JOBS} overrided even explicitly specified
+ Previously @env{$REDO_JOBS} overrided even explicitly specified
@option{-j} option. Fix that behaviour -- command line options must
precede environment variables.
@item @url{https://github.com/BLAKE3-team/BLAKE3, BLAKE3} replaces
@item tracing (@option{-x}) can be obviously done only for
non-executable @file{.do}
@item parallizable build is done only during @command{redo-ifchange} for
- human convenience: you can globally enable @env{REDO_JOBS}, but
+ human convenience: you can globally enable @env{$REDO_JOBS}, but
still do for example: @code{redo htmls infos index upload}
@end itemize