gittup/tup — comment on commit a30c881ea0d9254477a44f630edc81571609f4c1
File: src/tup/server/master_fork.c line 260
By gittup:

They just store the stdout/stderr from the sub-process until it exits.
As I understand the changes you have in your master branch for
output-buffering, this is similar. I think for some reason tmpfile()
couldn't be used (maybe Windows?), so I just put them in a tup-managed
tmp directory instead. The reason they went in is because I needed a
way to capture stdout from a run-script after the master-fork changes,
and there wasn't an easy way to communicate that information back to
the main tup process. If they go to temporary files, then we can also
get the benefit of output buffering. I am still working on the other
display changes you had in your branch, like updating the progress and
displaying the CC line after the command completes (this is still a
local working copy - may have something published this weekend).

Does that answer your question or is there some issue you're having with it?

On Mon, Oct 17, 2011 at 8:42 PM, Anatol

wrote:
> I am trying to understand what these output-%i and errors-%i files for? Why not to output to STDERR, STDOUT?
>
> --
> Reply to this email directly or view it on GitHub:
> https://github.com/gittup/tup/commit/a30c881ea0d9254477a44f630edc81571609f4c1#commitcomment-657278
>