./regress/tools, Ensure that the tools wrapper works as expected

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 2020.05.02nb1, Package name: regress-tools-2020.05.02nb1, Maintainer: pkgsrc-users
Required to build:
[pkgtools/cwrappers]

Version history: (Expand)


CVS history: (Expand)


   2021-05-24 21:56:06 by Thomas Klausner | Files touched by this commit (3575)
Log message:
*: recursive bump for perl 5.34
   2020-05-02 10:07:28 by Roland Illig | Files touched by this commit (1)
Log message:
regress/tools: reduce the number of backslashes in the code
   2020-05-02 10:03:17 by Roland Illig | Files touched by this commit (1)
Log message:
regress/tools: adjust COMMENT
   2020-05-02 09:24:32 by Roland Illig | Files touched by this commit (7) | Package removed
Log message:
regress: move tests for platform tools to tools-platform
   2019-05-22 22:47:05 by Roland Illig | Files touched by this commit (2)
Log message:
mk/tools: in the wrapper log, quote arguments containing = naturally
   2019-03-24 12:29:19 by Roland Illig | Files touched by this commit (3)
Log message:
mk/tools: correctly quote arguments in the tool wrapper log

Before, the tool arguments were written to the log as plain strings. Now
the arguments are properly quoted, which makes it possible to replay the
commands by copying them from the .work.log file.

This only affects tools that are shell builtins (echo, true, false), get
additional arguments (mkdir -p) or define a custom TOOLS_SCRIPT
(pkg-config, to set an environment variable; or autotools). Tools that
are symlinked to the real tool are not affected.

The calls to the compiler are already properly logged since cwrappers
takes care of that. This commit therefore makes the log entries for the
compilers and the other tools more similar.
   2019-03-24 09:40:08 by Roland Illig | Files touched by this commit (2)
Log message:
mk/tools: fix quoting when logging tool invocations

When a package or the infrastructure defined a tool with custom
TOOLS_ARGS or TOOLS_SCRIPT containing special characters, these could
lead to unintuitive interactions at the time when that tool invocation
was logged in the tool wrapper log. Some of the logging output ended up
on stdout, while some of the normal output ended up in the log, and parts
of the quoted arguments were even evaluated as shell commands.

The logging of the wrapped tool commands is not perfect yet, but at least
it's much more predictable now.
   2019-03-23 23:59:11 by Roland Illig | Files touched by this commit (3)
Log message:
regress/tools: show that TOOLS_SCRIPT is not always logged properly