On Fri, Feb 06, 2009 at 06:35:05PM -0800, James Keenan via RT wrote: > On Fri Jan 11 13:17:38 2008, jhobl...@ifa.hawaii.edu wrote: > > A log would be useful if it contained sufficient information to figure > > out why a test passed or failed. Similar to autoconf's config.log (an > > invaluable debugging tool when tracking down configuration problems). > > > > Is there any reason why this wouldn't suffice: > > perl Configure.pl --test --verbose 2>&1 | tee myconfiglog
Even that would be helpful but do you really want to document that for every possible shell that a user might be using and then have to point people at that document constantly? In my expirence it's nice to be able to just ask people to attach config.log from the build dir. > For some time now, we've also had Parrot::Configure::Trace, which > enables you to say: > > perl Configure.pl --configure_trace > > ... and then run methods to extract information about the status of the > Parrot::Configure object as it changes between configuration steps. That's exactly the sort of verbosity that you want to go into a log file. -J --
