# from Adam Kennedy
# on Wednesday 23 May 2007 06:40 pm:
>> 2. configure_requires in META.yml
>> (and support in M::B, M::I, CPAN(PLUS))
>
>Actually, configure_requires is implemented only in the CPAN client,
> not in the configure script.
By "support in M::B and M::I", I meant `./Build dist`.
But also...
>I should note that, even once configure_requires is added, things will
>still fail in the case where someone is running "perl (Configure).PL"
>by hand.
Sounds like we should add configure_requires checks to check_prereq() so
that this requirement will be more obvious once $magic_mb_version (e.g.
0.29 or so) is available.
>The difference between configure_requires and CPAN-driver upgrades is
>that one makes sure you have a new enough toolchain to build one
>specific module, and the latter is provided to solve the case of
>complete toolchain failure (which is the situation we are in now).
Right. In other words, the most important changes that need to get
pushed out are in CPAN(PLUS).pm, right? That is, they need to get
"must-upgrade awareness" and "configure_requires" so we can start
building an install-base of working clients.
What M::B and M::I need to do is A: set configure_requires at `./Build
distmeta` and B: (somewhat optionally) provide fallback checks for
configure_requires for the standalone "you should upgrade
Module::Build" message.
--Eric
--
"Insert random misquote here"
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
