Subject: | Version.pm thinks it's own version is uptodate when it isn't |
Hi,
it seems that the version comparison in version.pm doesn't quite work the way it should.
Using version.pm's own version comparison, it thinks that 0.7203 (last dev release $VERSION
string) is a more recent release than 0.73 (latest stable).
In fact, more oddities happen when we try variations thereof:
# it's a smaller version with one 0, but not with 2?
$ perl -Mversion -le'print qv("0.720")<=("0.73")'
1
$ perl -Mversion -le'print qv("0.7200")<=("0.73")'
# if both use two 0s, it's not smaller?
$ perl -Mversion -le'print qv("0.7200")<=("0.7300")'
$ perl -Mversion -le'print qv("0.7203")<=("0.73")'
# surely 0.7399 is bigger in any respect?
$ perl -Mversion -le'print qv("0.7203")<=("0.7399")'
$
Currently this stops version.pm (and modules using similar versioning
schemes) being updated on any CPAN/CPANPLUS that uses version.pm
to detect uptodateness.
For CPANPLUS, this is now the default with the new Module::Load::Conditional,
which is also part of 5.10.