Keep It Simple, Stupid | |
PerlMonks |
Re: What basic things should I know about versioning modules?by haukex (Archbishop) |
on Feb 23, 2017 at 12:50 UTC ( [id://1182640]=note: print w/replies, xml ) | Need Help?? |
Unfortunately, I can't find the source at the moment, but I remember reading somewhere that the "best" way to define a package version is simply
The reason being that this is the most compatible with the various Perl tools that parse code to find information on modules, and that tricks like parsing the version number out of an SVN tag ("$Revision$") may not work with all of them. I used a string in the above because using a decimal like 1.10 would print as "1.1" instead of "1.10". See "Version numbering" in perlmodstyle, which advocates version numbers like 1.00, 1.10, 1.11, 1.20 etc. Also, quoting from perlmodlib and Exporter:
There are also lots of other different versioning schemes in use by modules on CPAN. See also CPAN::Version.
In Section
Seekers of Perl Wisdom
|
|