Bug #24848 for CPAN: 2.000000 != 2.0.0

Thu Feb 08 13:03:18 2007 jdhedden [...] cpan.org - Ticket created

Subject:

2.000000 != 2.0.0

Text::Balanced 2.0.0 now makes use of 'version.pm': use version; $VERSION = qv('2.0.0'); In merging changes for 5.8.9, the following was done: +# I really don't want to bring the XS version module into maint. So for now, +# I'm commiting the sin of Bowdlerising Damian's module: +# use version; $VERSION = qv('2.0.0'); +$VERSION = 2.000000; As a result, the 'r' command for CPAN reports: Package namespace installed latest in CPAN file ... Text::Balanced 2 2.000000 DCONWAY/Text-Balanced-v2.0.0.tar.gz ... While the workaround is to quote the 2.000000 string, it is arguable that CPAN should see these two as equivalent.

Fri Feb 09 16:10:24 2007 ANDK [...] cpan.org - Correspondence added

This seems like an academic problem. If two modules have the same namespace and same version number, then they must be the very same module. This implies that they are bit for bit identical. This means that the version number is bit for bit identical. If there is a difference in the modules, then somebody has already goofed because then the version number must not be identical. And all parties involved in documenting version numbers do a better job when they clearly mark the difference than when they shove the difference under the carpet. This is what CPAN.pm at least in this specific situation does do a better job than other tools that report the two version strings as the same. Feel free to argue more about it, but for now I resolve the ticket as rejected because I do not think there is a bug in CPAN.pm. I'm open if you want to convince me otherwise.

Fri Feb 09 16:10:26 2007 The RT System itself - Status changed from 'new' to 'open'

Fri Feb 09 16:10:28 2007 ANDK [...] cpan.org - Status changed from 'open' to 'rejected'