Skip Menu |

This queue is for tickets about the DBM-Deep CPAN distribution.

Report information
The Basics
Id: 57621
Status: resolved
Priority: 0/
Queue: DBM-Deep

People
Owner: Nobody in particular
Requestors: haarg [...] haarg.org
Cc:
AdminCc:

Bug Information
Severity: Unimportant
Broken in: 1.0023
Fixed in: (no value)



Subject: Custom Module::Build subclass sets incorrect versions for provided modules
The Module::Build subclass sets the version that is recorded in the metadata to be the same as the main module's version. However, the modules have no $VERSION specified in themselves. This means the metadata doesn't reflect the actual files. One impact this has is that the CPAN shell can't check the module versions against the CPAN package details list and will always report the modules as in need of an upgrade. I think it would be preferable to either actually include the version numbers in the modules, or to remove the code in Build.PL that records the incorrect version numbers, leaving them as undefined.
On Tue May 18 22:46:59 2010, haarg wrote: Show quoted text
> The Module::Build subclass sets the version that is recorded in the > metadata to be the same as the main module's version. However, the > modules have no $VERSION specified in themselves. This means the > metadata doesn't reflect the actual files. > > One impact this has is that the CPAN shell can't check the module > versions against the CPAN package details list and will always report > the modules as in need of an upgrade. > > I think it would be preferable to either actually include the version > numbers in the modules, or to remove the code in Build.PL that records > the incorrect version numbers, leaving them as undefined.
I’ve just reset the version in PAUSE for all the sub-modules (the first time I’ve used that feature). I’ve also committed a change to github to leave the versions undef in future releases.