Re: FYI: fixing output of aclocal --verbose
Pavel> Another related question before I go ahead and enforce a single Pavel> standard. Pavel> Should versobe messages go to stdout or stderr? Automake uses Pavel> stdout, while all other auto* and aclocal use stderr. It doesn't matter to me. Please feel free to implement what you think is correct. Tom
Re: FYI: fixing output of aclocal --verbose
Pavel Roskin <[EMAIL PROTECTED]> writes: > In fact, when I run "autoreconf --verbose" I only want to know what it's > running. I can hardly imagine that I'll ever really need the verbose > output of all tools in the same time. I do! Then I'd suggest introducing --quiet too for silent, and have --verbose for full verbosity, default to saying what tool it is running. > If I know how exactly autoreconf is running automake, I'll rerun automake > with "--verbose". > > My suggestion is that autoreconf should > > 1) print what it's calling by default (except the calls to autoconf > --trace and others that don't change files). No redirections. > > 2) don't print what it's calling with --quiet. No redirections. > > 3) when called with --verbose, propagate it, print what it's calling and > redirect all to stderr. > > This would change the default behavior, but since the output of > autoreconf is intended mostly for humans, it shouldn't be an issue. Sounds pretty much the same :) That an OK in advance.
Re: FYI: fixing output of aclocal --verbose
> But since it transmits the --verbnse to its slaves and its slaves are > $verbosing on stderr, it should stay in stderr, so that messages > remain in order. A preferable solution for autoreconf, IMHO, but > somewhat more painful that the current status, would be to have > autoreconf redirect the verbose messages of the sub tools to stdout. > > Unfortunately, this would also mean redirect actually error messages > from subtools to stdout, which doesn't sound right. In fact, when I run "autoreconf --verbose" I only want to know what it's running. I can hardly imagine that I'll ever really need the verbose output of all tools in the same time. If I know how exactly autoreconf is running automake, I'll rerun automake with "--verbose". My suggestion is that autoreconf should 1) print what it's calling by default (except the calls to autoconf --trace and others that don't change files). No redirections. 2) don't print what it's calling with --quiet. No redirections. 3) when called with --verbose, propagate it, print what it's calling and redirect all to stderr. This would change the default behavior, but since the output of autoreconf is intended mostly for humans, it shouldn't be an issue. Regards, Pavel Roskin
Re: FYI: fixing output of aclocal --verbose
Pavel Roskin <[EMAIL PROTECTED]> writes: > Hello, Akim! > > Another related question before I go ahead and enforce a single standard. > > Should versobe messages go to stdout or stderr? Automake uses stdout, > while all other auto* and aclocal use stderr. I'm not consistent on this regard in the sense of a single answer: my point of view is that, of course, tools which _can_ produce on stdout must always $verbose on stderr. autoconf supports -o-, autoupdate too etc. As far as autoreconf is concerned, I'd say the natural answer is stdout, since it cannot produce actual output on stdout: it makes it easier to | less. But since it transmits the --verbnse to its slaves and its slaves are $verbosing on stderr, it should stay in stderr, so that messages remain in order. A preferable solution for autoreconf, IMHO, but somewhat more painful that the current status, would be to have autoreconf redirect the verbose messages of the sub tools to stdout. Unfortunately, this would also mean redirect actually error messages from subtools to stdout, which doesn't sound right.
Re: FYI: fixing output of aclocal --verbose
Hello, Akim! > Pavel> Hello! Aclocal didn't follow the GNU standard for the output > Pavel> of non-interactive programs. Now all messages printed by > Pavel> "aclocal --verbose" will start with "aclocal: " to make it > Pavel> easier to find them in the autoreconf output. > > While you're at it, I'd like to say that it is not right to display > `aclocal:', it should be basename $0. Not that automake and aclocal > are often installed under some other name, but... Another related question before I go ahead and enforce a single standard. Should versobe messages go to stdout or stderr? Automake uses stdout, while all other auto* and aclocal use stderr. Regards, Pavel Roskin
Re: FYI: fixing output of aclocal --verbose
> "Pavel" == Pavel Roskin <[EMAIL PROTECTED]> writes: Pavel> Hello! Aclocal didn't follow the GNU standard for the output Pavel> of non-interactive programs. Now all messages printed by Pavel> "aclocal --verbose" will start with "aclocal: " to make it Pavel> easier to find them in the autoreconf output. While you're at it, I'd like to say that it is not right to display `aclocal:', it should be basename $0. Not that automake and aclocal are often installed under some other name, but...
