# New Ticket Created by James Keenan
# Please include the string: [perl #45523]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=45523 >
Configure.pl has long operated as a harness for the running of
individual configuration steps, currently 58 in number. Just when
Perl 5's Test::Harness module tries to run a series of individual
test files even when one of those test files has died, so too does
Parrot's Configure.pl attempt to run the whole series of individual
configuration steps even when one or more steps has failed.
Unlike Test::Harness, however, Configure.pl is not a very smart
harness. It doesn't regularly inform the user of a failure in an
individual configuration step. We need to change this, but because
of the complexity of the configuration process and the fact that it
works well for most Parrot developers most of the time, we need to
make changes that are incremental in nature.
This RT proposes an incremental change in Configure.pl's behavior.
Currently, Configure.pl prints the following cheery message (from
Parrot::Configure::Messages::print_conclusion()) to STDOUT whether
all configuration steps have passed or not:
#####
Okay, we're done!
You can now use `$make' to build your Parrot.
(NOTE: do not use `$make -j <n>'!)
After that, you can use `$make test' to run the test suite.
Happy Hacking,
The Parrot Team
#####
(Substitute the user's make-equivalent for $make.)
At the very least, we should list any configuration steps that have
failed and advise the user that 'make' is dubious.
Assignment: Revise Configure.pl and its underlying modules to inform
the user of configuration steps that have failed.
kid51
