diff options
| author | Boris Kolpackov <boris@codesynthesis.com> | 2018-05-02 13:54:51 +0200 |
|---|---|---|
| committer | Boris Kolpackov <boris@codesynthesis.com> | 2018-05-02 13:54:51 +0200 |
| commit | 0881ca0a229f29d6a02b24ba0bb3e19f968293de (patch) | |
| tree | 524edd223a083413b3572781b445827701fa131f /doc | |
| parent | 0c436eeb63fecf1a63a7dfc2be946beb2718f36d (diff) | |
Spec changes to versioning epoch format
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/manual.cli | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/manual.cli b/doc/manual.cli index 524b817..0d5b5ab 100644 --- a/doc/manual.cli +++ b/doc/manual.cli @@ -33,7 +33,7 @@ versioning and that allows automation of many version management tasks. See The \c{bpkg} package version has the following form: \ -[<epoch>~]<upstream>[-<prerel>][+<revision>][#<iteration>] +[+<epoch>-]<upstream>[-<prerel>][+<revision>][#<iteration>] \ The \i{epoch} part should be an integer. It can be used to change to a new @@ -89,9 +89,9 @@ It is assumed that this version will always be greater than the stub version. When displaying the package version or when using the version to derive the file name, zero \i{epoch}, \i{revision}, and \i{iteration} are omitted (even if they were explicitly specified, for instance, in the package manifest). For -example, \c{0~1.2.3+0} will be used as \c{libfoo-1.2.3}. +example, \c{+0-1.2.3+0} will be used as \c{libfoo-1.2.3}. -\N|This versioning scheme and the choice of delimiter characters (\c{~-+}) +\N|This versioning scheme and the choice of delimiter characters (\c{.-+}) is meant to align with semantic versioning.| Some examples of versions: @@ -105,11 +105,11 @@ Some examples of versions: 1.2.3-alpha.1 1.2.3-beta.1 1.2.3+1 -1~1.2.3 -1~1.2.3-alpha.1+3 -1.2.3#1 ++1-1.2.3 ++1-1.2.3-alpha.1+3 ++1.2.3#1 1.2.3+1#1 -1~1.2.3+1#2 ++1-1.2.3+1#2 \ The version sorting order is \i{epoch}, \i{upstream}, \i{prerel}, |