Tim Hockin ece68cf833 Fix update-vendor.sh logging ...

Previously it would corrupt the log when it ran stuff like:
    go mod tidy >> "${LOG_FILE}" 2>&1
because this would reopen the file.  Also, if that failed, the `finish`
function would be called ALSO with output to the log.

Now we let &1 and &2 always be the log, and &11 and &22 are the real
stdout/stderr, which means we have to say that explicitly when we want
output.

No, I cannot do `OUT="&11"` - I would have to use `eval` to make that
work.

2023-05-22 14:51:30 -07:00

16 KiB

Executable File

Raw Blame History

View Raw