Andreas J. Koenig wrote:
I've tracked it down.
Awesome! Thanks for your efforts!
See, this holds for v-strings:
v2.5 == v2.0005
How is that relevant? You mean that CPAN.pm converts 2.005 into
v2.005? If it does, then that's fine (even if just by accident).
And this is true in
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
Andreas J. Koenig wrote:
If that's the case then I wonder why `r` (reinstall
recommendations) in `cpan` on my system (CPAN.pm 1.76_02, Perl
5.8.8) does NOT list Mail::SPF as being out of date, even though I
have the exact same version of Mail::SPF installed as the
complainant (2.004),
Julian Mehnle wrote:
But doesn't `perldoc version` say that I am strongly encouraged to use the
qv() operator if I wanted to use extended versions? Does that recommen-
dation perhaps need to be further qualified then?
You skipped over the previous paragraph:
Whichever of the two types of
On Wed, 02 May 2007 21:32:13 -0400, John Peacock [EMAIL PROTECTED] said:
I'd have to know what release of CPAN you are using, since those two version
objects are equivalent.
I know that you believe that they are equivalent but this is not the
question. CPAN.pm honours the string
Andreas J. Koenig wrote:
When CPAN.pm calculates the number, it never has trailing zeroes, when
version.pm calculates the number, it often appends trailing zeroes.
No longer the case; version-0.7203 now returns the same string that was
used to initialize a version object as the default
John Peacock wrote:
Eric Wilhelm wrote:
The question may be whether the version.pm / CPAN code is honoring
your VERSION line correctly. Though, possibly that should be
qv('v2.4.0'). John?
I'd have to know what release of CPAN you are using, since those two
version objects are
John Peacock wrote:
version-0.7203 now returns the same string that was used to initialize a
version object as the default stringification. The internal representa-
tion is no longer overtly visible (though you can get it via -numify or
-normal).
Well, that's only with version-0.7203+,
# from Julian Mehnle
# on Wednesday 02 May 2007 03:34 pm:
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:
