# from David Cantrell
# on Friday 28 August 2009 04:10:
>> I guess maybe. It still seems arbitrary, and my point was that it
>> is a workaround to the fact that it's currently difficult for a
>> module to do "the right thing" to even compare its version against
>> the index.
>
>I'd restrict it to only those modules that are needed to install
> stuff:
>
> CPAN.pm
> ExtUtils::MakeMaker
> Module::Build
> CPANPLUS
We've already solved the 'install-side' need with configure_requires.
I was talking about the `./Build dist` (author) side of things (from the
observation that the OP had run into a bug which would have been
avoided by upgrading M::B before rolling a dist.)
Authors using an old Module::Build won't be releasing dists with M::B in
configure_requires until they upgrade. That might happen automatically
if they install some new code from the CPAN which has M::B in its
configure_requires, but that's a combination of happy accidents.
And, if we were to pretend that M::B author tools were split off into a
separate distribution, having CPAN.pm warn you about a new M::B
wouldn't do any good, plus people would be confused when their `./Build
dist` suddenly started complaining about needing to install something
extra (which brings me back to the bit about users setting a preference
about which CPAN client to use.)
--Eric
--
"...the bourgeoisie were hated from both ends: by the proles, because
they had all the money, and by the intelligentsia, because of their
tendency to spend it on lawn ornaments."
--Neal Stephenson
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
