Re: [Module::Build] M::B and version.pm

[Randy W. S. <ml...@th...>]

David E. Wheeler wrote:
> On Feb 22, 2006, at 12:54, John Peacock wrote:
> 
>> That would be $v->normal, but that isn't the problem.  The problem is 
>> that M::B doesn't want to carry around the version object as an 
>> object, and so has to convert into something non-magical.
> 
> Right.
> 
>> If Ken and/or Randy want to tell me whether they want to hold 0.28 for 
>> the fully debugged and thought out version object support, I will do 
>> what I can to get that working.
> 
> I think that this is the way that it will have to go before long. What 
> with Damian encouraging everyone to use version.pm for their version 
> objects, we're already seeing distributions such as "Class-Std-v0.0.8" 
> (what's with the "v"?). After the next release of Module::Build, if a 
> new version of Class::Std is released, it will be "Class-Std-000009". 
> Some might find that annoying. And why very few modules use version.pm 
> now, I would expect that to start to change in the next year.

I'm no expert in regards to versions, and I don't know as much as I 
should or need to to make an intelligent decision. My most general 
opinion on the issue: 1) especially with the recent hoopla, 
Module::Build must produce results equivalent to MakeMaker unless there 
is a very good reason to be different; 2) it must produce usable results 
(eg META.yml) that can be used by CPAN.pm, CPANPLUS, etc.; and 3) it 
must work with perl versions back to 5.005x.

I don't know if this means operating in different modes under different 
circumstances, eg different behavior on perl 5.10 vs 5.6, or different 
behavior in the presence of version.pm, or different behavior depending 
on whether the distribution in question 'use version;', etc.

This is just an opinion. Any resemblance to an actual requirement or 
solution are unintentional. Please consult Ken for approval or 
validation. =)

Randy.