>>>>> On Wed, 15 Feb 2006 07:36:17 -0500, John Peacock <[EMAIL PROTECTED]> said:
jp> Andreas J. Koenig wrote:
>>>>>>> On Wed, 15 Feb 2006 13:29:34 +1100, Adam Kennedy <[EMAIL PROTECTED]>
>>>>>>> said:
>> > So as a result, any MB-using dist cannot be installed on any current
>> > production Perl. Installation requires an undocumented (to the
>> > installer) undeclared non-core module MB to be hand-installed because
>> > any of these dists will work.
>>
>> CPAN.pm 1.83_56 introduced a protection against this sometimes missing
>> prerequisite declaration. 1.84 is really close to a release, so this
>> gap is closed then.
jp> Actually, I was going to point out that I took one of the rare machines
that I
jp> have access to that isn't infected with my entire toolchain and installed
jp> Bundle::CPAN. The very last thing it installed was Module::Build itself;
I was
jp> trying to see how long the Bundle::CPAN that is distributed with CPAN has
jp> included M::B, but search.cpan.org is having some issues at the present
time. :(
It entered 2005-12-19, short before 1.80_57. But note, that the
protection I was talking about is not the fact that M:B is in the
Bundle:CPAN. The protecion looks instead like so:
if (-f "Build.PL" && ! -f "Makefile.PL" && ! exists
$req->{"Module::Build"}) {
$CPAN::Frontend->mywarn(" Warning: CPAN.pm discovered Module::Build as
".
"undeclared prerequisite.\n".
" Adding it now as a prerequisite.\n"
);
This code ensure that M:B gets installed right at the moment where it
is actually required.
--
andreas
