Joey Hess <jo...@debian.org> writes: > Joey Hess wrote: >> (The implementation needs to be improved; it should read both stdout >> and stderr and multiplex them properly. And it should check if stdout >> is not to a TTY, and if so avoid munging the build log output. The only >> other problem is that `make` outputs the lines it runs to stderr and so >> those continue to pollute the build display.)
> Also it could save the whole log to someplace when minimizing the > console output, to refer back to. Perhaps ../$package_$version.buildlog > (which gets a step closer to including that in the dsc and uploading > local build logs..) debuild, pbuilder, and related packages currently use ../<package>_<version>_<arch>.build for this output. Maybe the lower-level build architecture should take over maintaining that log file instead and those tools should be modified to assume that's already happening and move that log file around like the other build products? -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87siyd6xta....@windlord.stanford.edu
