1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
|
SemVer version 0.7.0
====================
This module subclasses [`version`] to create semantic versions, as defined by
the [Semantic Versioning 2.0.0 Specification]
The salient points of the specification, for the purposes of version
formatting, are:
1. A normal version number MUST take the form X.Y.Z where X, Y, and Z are
non-negative integers, and MUST NOT contain leading zeroes. X is the major
version, Y is the minor version, and Z is the patch version. Each element
MUST increase numerically.
For instance: `1.9.0 < 1.10.0 < 1.11.0`.
2. A pre-release version MAY be denoted by appending a hyphen and a series
of dot separated identifiers immediately following the patch version.
Identifiers MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-].
Identifiers MUST NOT be empty. Numeric identifiers MUST NOT include leading
zeroes. Pre-release versions have a lower precedence than the associated
normal version. A pre-release version indicates that the version is
unstable and might not satisfy the intended compatibility requirements
as denoted by its associated normal version.
Examples: `1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-0.3.7, 1.0.0-x.7.z.92`.
3. Build metadata MAY be denoted by appending a plus sign and a series of
dot separated identifiers immediately following the patch or pre-release
version. Identifiers MUST comprise only ASCII alphanumerics and hyphen
[0-9A-Za-z-]. Identifiers MUST NOT be empty. Build metadata SHOULD be
ignored when determining version precedence. Thus two versions that differ
only in the build metadata, have the same precedence.
Examples: `1.0.0-alpha+001, 1.0.0+20130313144700, 1.0.0-beta+exp.sha.5114f85`.
4. Precedence refers to how versions are compared to each other when ordered.
Precedence MUST be calculated by separating the version into major, minor,
patch and pre-release identifiers in that order (Build metadata does not
figure into precedence). Precedence is determined by the first difference
when comparing each of these identifiers from left to right as follows:
Major, minor, and patch versions are always compared numerically.
Example: `1.0.0 < 2.0.0 < 2.1.0 < 2.1.1`.
When major, minor, and patch are equal, a pre-release version has lower
precedence than a normal version.
Example: `1.0.0-alpha < 1.0.0`.
Precedence for two pre-release versions with the same major, minor, and
patch version MUST be determined by comparing each dot separated identifier
from left to right until a difference is found as follows: identifiers
consisting of only digits are compared numerically and identifiers with
letters or hyphens are compared lexically in ASCII sort order. Numeric
identifiers always have lower precedence than non-numeric identifiers. A
larger set of pre-release fields has a higher precedence than a smaller
set, if all of the preceding identifiers are equal.
Example: `1.0.0-alpha < 1.0.0-alpha.1 < 1.0.0-alpha.beta < 1.0.0-beta < 1.0.0-beta.2 < 1.0.0-beta.11 < 1.0.0-rc.1 < 1.0.0`.
[`version`]: http://search.cpan.org/perldoc?version
[Semantic Versioning 2.0.0 Specification]: http://semver.org/spec/v2.0.0.html
Installation
============
To install this module, type the following:
perl Build.PL
./Build
./Build test
./Build install
Dependencies
------------
SemVer requires version.
Copyright and License
---------------------
Copyright (c) 2010-2018 David E. Wheeler. Some Rights Reserved.
This module is free software; you can redistribute it and/or modify it under
the same terms as Perl itself.
|
