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). <a href="http://version.pm">version.pm</a> tries to deal with some of the problems caused by such attempts but it still isn't a perfect solution.<br>
<br>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.<br>
<br>Note that<br><br> our $VERSION= 1.02_013;<br><br>is exactly the same as<br><br> our $VERSION= 1.02013;<br><br>the underscore disappears from the value and is only apparent in the source code. <br><br>On Thu, Jan 15, 2009 at 5:44 PM, Christopher Howard <span dir="ltr"><<a href="mailto:choward@indicium.us">choward@indicium.us</a>></span> wrote:<br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">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:<br>
<br>
...<br>
VERSION => 1.4,<br>
...<br>
<br>
But if the version number of my app is, say 0.1.2, what should the line look like?<br>
<br>
VERSION => '0.1.2',<br>
<br>
or<br>
<br>
VERSION => 0.001.002<br>
<br>
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.<br>
<br>
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. =]<br>
<br></blockquote></div><br>