SPUG: version numbers and MakeMaker

Tye McQueen tyemq at cpan.org
Thu Jan 15 18:17:59 PST 2009

I would discourage using version numbers that aren't numbers and that don't
sort properly when treated as strings (which means a fixed number of digits
per component).  version.pm tries to deal with some of the problems caused
by such attempts but it still isn't a perfect solution.

My version numbers are usually like 1.001, 1.01_001, or 1.001_001 and I skip
subversion numbers that are multiples of ten.  So version numbers jump from
1.01_019 to 1.01_021.  I also leave enough digits per component such that
the leading 0 almost never gets incremented.

Note that

    our $VERSION= 1.02_013;

is exactly the same as

    our $VERSION= 1.02013;

the underscore disappears from the value and is only apparent in the source

On Thu, Jan 15, 2009 at 5:44 PM, Christopher Howard <choward at indicium.us>wrote:

> I'm creating my first Makefile.PL, and had a question: There is one
> key/value pair for the version number. I have seen it like this in examples:
> ...
> VERSION => 1.4,
> ...
> But if the version number of my app is, say 0.1.2, what should the line
> look like?
> VERSION => '0.1.2',
> or
> VERSION => 0.001.002
> Or does it even matter? I'm inclined toward '0.1.2' because I prefer that,
> and when I tried it with make dist the archive name came out looking the way
> I prefer.
> You know, if I ever get really good at MakeMaker, I think I'm going to
> volunteer to update the documentation with lots of examples. =]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/spug-list/attachments/20090115/a70c48a1/attachment.html>

More information about the spug-list mailing list