X-Git-Url: http://www.git.cypherpunks.ru/?a=blobdiff_plain;f=doc%2Fnews.texi;h=1bcec11f373d68bfa5c287b0db21186f8dc3ca47;hb=b2b1d51fb5968a6cfa86bf17c9f7d1d0b8a1cb2a;hp=3574f79515eb9bf01d50e37a92959fe19c49dc5d;hpb=3fa21c8c7e74798a07fbcc99030bae7c2505f76d;p=goredo.git diff --git a/doc/news.texi b/doc/news.texi index 3574f79..1bcec11 100644 --- a/doc/news.texi +++ b/doc/news.texi @@ -1,11 +1,181 @@ @node News +@cindex news @unnumbered News +@anchor{Release 1_27_0} +@section Release 1.27.0 +@itemize +@item + Improved out-of-date check and @file{.do} files search performance, + because of caching their results. +@end itemize + +@anchor{Release 1_26_0} +@section Release 1.26.0 +@itemize +@item + Debug output contained colour-related attribute even if + @env{$NO_COLOR=1} was set. +@item + Updated dependant libraries. +@end itemize + +@anchor{Release 1_25_0} +@section Release 1.25.0 +@itemize +@item + Target's lock file requires a token from the jobserver now. So + amount of simultaneously opened lock files depends on job slots + available. +@end itemize + +@anchor{Release 1_24_0} +@section Release 1.24.0 +@itemize +@item + @command{redo-cleanup tmp} also removes temporarily (@code{$3}) + created directories. +@end itemize + +@anchor{Release 1_23_0} +@section Release 1.23.0 +@itemize +@item + @command{redo-ifchange}'s @option{-f} option forces each target + rebuilding. Comparing to @command{redo}, it will parallelize the + process. +@item + Inode's number is also stored as dependency information, just to + prevent possible @code{ctime} collision of two files. +@item + Performance optimization: do not use target's temporary output file + at all, if its hash equals to already existing target's one. Just + touch existing target file instead. +@end itemize + +@anchor{Release 1_22_0} +@section Release 1.22.0 +@itemize +@item + @code{flock} locks replaced with POSIX @code{fcntl} ones. + They could be more portable. +@item + @command{redo-depfix} command appeared, that traverses through all + @file{.redo} directories and their dependency files, checks if + corresponding targets has the same content but different + @code{ctime}/@code{mtime} values and rewrites dependencies with that + updated inode information. +@item + With @env{$REDO_STOP_IF_MODIFIED=1} environment variable redo will + stop and fail if it meet externally modified file. By default user + is only warned about it, but building continues for convenience. +@end itemize + +@anchor{Release 1_21_0} +@section Release 1.21.0 +@itemize +@item + @env{$REDO_INODE_NO_TRUST} is replaced with @env{$REDO_INODE_TRUST} + environment variable, that takes either @code{none}, or @code{ctime} + (the default one), or @code{mtime} (new one). Check documentation's + separate page about that option. +@end itemize + +@anchor{Release 1_20_0} +@section Release 1.20.0 +@itemize +@item + Print warning message if both ifcreate and ifchange records were + discovered after the target is done. +@end itemize + +@anchor{Release 1_19_0} +@section Release 1.19.0 +@itemize +@item + Skip target itself, when searching for corresponding @file{.do} + file. For example @file{default.do} must use @file{../default.do} + instead of the self. +@end itemize + +@anchor{Release 1_18_0} +@section Release 1.18.0 +@itemize +@item + Fix regression of known OODs passing since 1.3.0, that leads to + rebuilding of already built targets. +@end itemize + +@anchor{Release 1_17_0} +@section Release 1.17.0 +@itemize +@item + If @command{redo*} process is killed, then it sends @code{SIGTERM} + to all his children too, properly terminating the whole job queue. +@end itemize + +@anchor{Release 1_16_0} +@section Release 1.16.0 +@itemize +@item + Unexistent targets are considered always out-of-date, as it should be. +@item + Do not panic if @env{$REDO_LOGS=1} and we were unable to start the command. +@end itemize + +@anchor{Release 1_15_0} +@section Release 1.15.0 +@itemize +@item + Explicitly check if @code{$1} target is touched and then fail. + Previously we check if @code{$1} was only altered. +@end itemize + +@anchor{Release 1_14_0} +@section Release 1.14.0 +@itemize +@item + Fixed @command{redo-ifcreate}'s targets proper relative paths to the target. +@end itemize + +@anchor{Release 1_13_0} +@section Release 1.13.0 +@itemize +@item + Use @file{.log-rec} extension, instead of @file{.log.rec}, that + won't collide with already existing @file{.log} and @file{.rec} in + @file{.redo} directory. +@end itemize + +@anchor{Release 1_12_0} +@section Release 1.12.0 +@itemize +@item + Fix possible lack of success finish message printing if any of + targets fail. +@end itemize + +@anchor{Release 1_11_0} +@section Release 1.11.0 +@itemize +@item + Fix nasty bug with incorrect @file{.redo/tgt.rec} files renaming. +@end itemize + +@anchor{Release 1_10_0} +@section Release 1.10.0 +@itemize +@item + @command{redo-cleanup} now also cleans @file{.redo/tgt.log.rec} files. +@item + Recursive logs do not require @file{.redo/tgt.rec} existence anymore. +@end itemize + @anchor{Release 1_9_0} @section Release 1.9.0 @itemize @item - Do not enable command lines options not applicable to the command. + Do not enable command line options not applicable to the command. For example @option{-j} option is only applicable to @command{redo} and @command{redo-ifchange} commands. @item @@ -14,6 +184,16 @@ @item @option{-logs} option is renamed to @option{-k} @item @option{-silent} option is renamed to @option{-s} @end itemize +@item + When @code{stderr} logs are kept, all environment variables, working + directory, command line arguments, start/finish times, duration, + participated PIDs, return codes are saved in corresponding + @file{.redo/tgt.log.rec} file. Some of them can be viewed with + @option{-c} option to @command{redo-log}. +@item + @command{redo-log}'s @option{-r} option allows recursive, indented + viewing of the whole redo commands invocations for the given target + in serialized way. @end itemize @anchor{Release 1_8_0}