This follow up of mine might be slightly off-topic for the module-build
list, but as it still pertains to this thread, I'd rather avoid fragmen-
ting it.

Andreas J. Koenig wrote:
> Julian Mehnle said:
> > recently someone reported a problem with one of my modules that might
> > indicate an issue with how CPAN, Module::Build's META.yml generator,
> > and version.pm interact.  Please see the rt.cpan.org ticket included
> > below.
> >
> > The Mail-SPF 2.004 distribution package was built with Module::Build
> > 0.26, as that is the least outdated version available in Debian. :-(
> >
> > Is it likely that M::B 0.26's META.yml generator is badly interacting
> > with version.pm-based version numbers (`use version; our $VERSION =
> > qv('2.004');`) and CPAN is really expecting a version.pm-style version
> > number in META.yml (here: "v2.004")?  Or why would CPAN report a
> > version mismatch for "v2.004" vs "2.004000"?
>
> This looks like a mismatch of the way how CPAN.pm and version.pm handle
> the stringification of the numification of version objects.
>
> When CPAN.pm calculates the number, it never has trailing zeroes, when
> version.pm calculates the number, it often appends trailing zeroes.
>
> There's not much you can do about it. Some day CPAN.pm will switch to
> using version.pm directly and hopefully this will then resolve your
> issue. But I'm not yet up to it.

Now that Mail-SPF v2.005 has been released (with META.yml fixed to read
"version: v2.005" instead of "version: 2.005000"), I am still having
trouble with CPAN.pm:

| cpan[1]> r Mail::SPF
| CPAN: Storable loaded ok (v2.15)
| Going to read /home/julian/.cpan/Metadata
|   Database was generated on Tue, 19 Jun 2007 21:08:40 GMT
| 
| Package namespace         installed    latest  in CPAN file
| Mail::SPF                    v2.005     2.005  
JMEHNLE/mail-spf/Mail-SPF-v2.005.tar.gz
| 1 installed module has a version number of 0

How come CPAN.pm detects the "latest" version (on CPAN) as "2.005" rather
than "v2.005"?  Doesn't CPAN.pm read the META.yml on CPAN to determine the
version number?

Julian.

Attachment: pgp9mQd5J9YfC.pgp
Description: PGP signature

Reply via email to