On Fri, Aug 28, 2009 at 1:25 PM, Bill Ward<[email protected]> wrote:
> On Fri, Aug 28, 2009 at 9:02 AM, Eric Wilhelm<[email protected]> wrote:
>> # 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.)
>
> Can PAUSE detect the version of M::B or EU::MM that the author used,
> and warn accordingly or even reject it?
Well, one can use the META.yml information about what software
generated it, but it's not entirely accurate. I believe this was
something Eric and others took a look at, in order to notify authors
with old toolchains.
>
