Re: dist_version_from / module_name

# from John Peacock
# on Thursday 10 July 2008 19:52:

>But, I think this is a serious regression, since the documentation for
>dist_version_from() clearly states that:
>> The version is extracted from the specified file according to
>> the same rules as ExtUtils::MakeMaker and "CPAN.pm".  It
>> involves finding the first line that matches the regular
>> expression
>>
>>     /([\$*])(([\w\:\']*)\bVERSION)\b.*\=/
>
>and doesn't say anything about the module_name being involved.

Well, I would say that either the documentation is wrong or the 
ModuleInfo code is wrong because the treatment was always looking at 
the module/file name in deciding which of however many seen VERSION 
lines to treat as what.

See r10222.

So, this was me trying to enable a script to be packaged with the same 
formality as a module - e.g. with tests and declared dependencies - as 
a simple way to start a distribution and also as a matter of making the 
script be addressable via the CPAN client.

And despite my investigation of mldistwatch in trying to understand what 
PAUSE would think of it, apparently such a thing still won't get 
indexed - for reasons which I apparently cannot decipher without 
replicating the PAUSE machine.

And this is the only feature I've tried to add to Module::Build in the 
past 1.5 years.

So, I guess just revert that.  I'm out.

--Eric
-- 
Introducing change is like pulling off a bandage: the pain is a memory
almost as soon as you feel it.
--Paul Graham
---------------------------------------------------
    http://scratchcomputing.com
---------------------------------------------------