On Behalf Of Alex Gough:
# I've modified Configure.pl to take defaults from a previous build (if
# there was one). This should play nicely with hints, and '--defaults'
# by doing the Right Thing. I've added a '--nopolicy' option to disable
# this.
FYI, this is sitting around the top of my stack; however, I'm waiting
for discussion on what to call this to shake out.
Something in the implementation I'd like to bring up: is there a reason
this is loaded before defaults are chosen, instead of roughly where
hints are pulled in? (Probably after, since hints files may now provide
things besides defaults, like commands to run compilers. The
hints-loaded values can still be overridden by the policy, however.)
The code could look like this:
(pull in hints file)
if(-e "Parrot/Config.pm") {
eval "use Parrot::Config";
%c=%pConfig;
}
(etcetera)
except that "Parrot/Config.pm" isn't portable to VMS. Ack. Probably
some File::Spec tomfoolery will be needed.
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
They *will* pay for what they've done.
