On Mon, 8 Apr 2002, Stas Bekman wrote: > Ged Haywood wrote: >> Compilations should be SILENT unless something goes wrong. > > The build process takes time, if you don't give an indication > of what's going on users will try to do funky things. Since the > build process is comprised of many small sub-processes you cannot > really use something like completion bar.
As someone said, redirect the output to a temporary location. But, add to that one of those little | bars, which turns one position every time another build step completes (each file compiled, each dependancy file built, etc.). However, in the case of an error, I would want the whole thing available. Possibly something along the lines of, the last build step and all output from then on printed to stdout (or stderr), ended with, "For the full build log, see /tmp/mod_perl.build.3942" or some such. > Also remember that mod_perl build prints very little, > it's the compilation messages that generated most of the output. > p.s. I don't recall seeing silent build processes at all. The only ones I've seen went too far the other way. I especially loved the one which used a shell script, which started out with a dozen large shell functions, then an 'exec >/dev/null 2>/dev/null', then a half-dozen more large shell functions, and ending with 'main "$@"'. When the shell script finished, its caller checked its exit code, and reported 'done.' or 'failed.' as appropriate. Admittedly, I wouldn't have minded too much, except that I'd gotten the latter answer. Ed
