|Version 3 (modified by coke, 5 years ago)|
Parrot Based Config
Discussion about the Roadmap item for 3.0
Things that should be changed (or at least discussed), regardless of the tools used to implement the configure system.
- Should be able to override hints files from the command line. Let the user shoot themselves in the foot.
- Don't run configure tests as part of 'make test' - if the parrot tests pass, Configure worked.
- use a standard mechanism for parsing options, to unify the true/false/set/unset/use/don't syntax.
- Don't rely on perl's Config for information.
See issues http://rt.perl.org/rt3/Ticket/Display.html?id=56634 , especially: don't use Configure.pl to generate files that should be generated by simple makefile rules. Don't require --maintainer, have config just autodetect and create appropriate rules.