Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change
 
PerlMonks  

Re: Can't use three part version number for CPAN modules

by Perl Mouse (Chaplain)
on Jan 04, 2006 at 13:04 UTC ( #520885=note: print w/replies, xml ) Need Help??


in reply to Can't use three part version number for CPAN modules

Here's what I got from the PAUSE indexer report. A status of "Falling revision number". The Indexer was somehow converting "0.0.3" to "0.000003", and that being less than "0.01", hence the error.
While I think that converting "0.0.3" to "0.000003" isn't the correct way (and the PAUSE indexer contains more 'surprises', for instance, it thinks that "0.2" is a newer version than "0.11", because it considers "0.2" to be a short hand for "0.002" and "0.11" a short hand for "0.011" - not that this is an idea of PAUSE - Andreas is just doing what perl is doing itself), I think that most people will consider "0.01" to be a newer release than "0.0.3". "0.01" reads as major release 0, minor release 1. "0.0.3" reads as major release 0, minor release 0, patch level 3. I don't think you should interpret Damian's suggestion to use three part version numbers as an invitation to just take your two part version number and insert an extra dot. I would consider "0.01" and "0.1.0" to be equivalent, and hence, "0.0.3" to be an older release.

I suggest you keep 0.01 in your CPAN dir, and name your new release "0.1.3", or "0.2.3", and count from there.

Perl --((8:>*
  • Comment on Re: Can't use three part version number for CPAN modules

Replies are listed 'Best First'.
Re^2: Can't use three part version number for CPAN modules
by arc_of_descent (Hermit) on Jan 04, 2006 at 13:48 UTC
    I think that most people will consider "0.01" to be a newer release than "0.0.3". "0.01" reads as major release 0, minor release 1. "0.0.3" reads as major release 0, minor release 0, patch level 3. I don't think you should interpret Damian's suggestion to use three part version numbers as an invitation to just take your two part version number and insert an extra dot. I would consider "0.01" and "0.1.0" to be equivalent, and hence, "0.0.3" to be an older release.

    Thanks for the insight.


    --
    Rohan

Re^2: Can't use three part version number for CPAN modules
by Anonymous Monk on Jan 04, 2006 at 23:56 UTC
    > While I think that converting "0.0.3" to "0.000003"
    > isn't the correct way

    It's the official way. Please read perldoc version.

    > it thinks that "0.2" is a newer version than "0.11",
    > because it considers "0.2" to be a short hand for "0.002"
    > and "0.11"

    Wrong. It considers 0.2 > 0.11 because perl does:

    % perl -le 'print 0.2 > 0.11 ? "T" : "F"'
    T

    > most people will consider "0.01" to be a newer release
    > than "0.0.3".

    Thank you! I couldn't agree more!

    > I would consider "0.01" and "0.1.0" to be equivalent

    Sorry, the factor 1000 has been chosen to be the perl mapping for each dot in the version string.

    > I suggest you keep 0.01 in your CPAN dir, and name your
    > new release "0.1.3", or "0.2.3"

    Sorry, it would have to be at least a little bit more than 0.10.0, because 0.10.0 is the equivalent of 0.010000 and as such is exactly numerically equal to 0.01.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://520885]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others studying the Monastery: (4)
As of 2020-10-26 08:04 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    My favourite web site is:












    Results (250 votes). Check out past polls.

    Notices?