# from Ken Williams
# on Saturday 31 March 2007 08:12 am:
>On Mar 31, 2007, at 6:51 AM, Adam Kennedy wrote:
>> It may not be your line of code that failed, but it's still your
>> responsibility for breaking the toolchain in your Build.PL, and
>> thus the bug is correctly yours.
Are we talking about the bootstrapping problem again? Do CPAN&+ not
read META.yml?
>The main reason we can't ever default to --allow_mb_mismatch=1 is
>that we don't promise binary compatibility of the _build/ directory
>across releases.
So, we need to upgrade Module::Build before Build.PL runs, but don't
know what version we want until we're running Build.PL, right?
Could we solve this if Module::Build could download and install a newer
version of itself?
How can we access the ARGV with which `perl Build.PL` was run? If we
were to exec('perl', @original_perl_args) after upgrading MB, would
that do the trick?
Of course, the MB versions that don't self-upgrade wouldn't be fixed,
but perhaps we can get CPAN and CPANPLUS to depend on a new version of
MB in order to get the solution out sooner?
--Eric
--
Turns out the optimal technique is to put it in reverse and gun it.
--Steven Squyres (on challenges in interplanetary robot navigation)
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
