summaryrefslogtreecommitdiffstats
path: root/specs/spf-2.0/metadata.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'specs/spf-2.0/metadata.mdwn')
-rw-r--r--specs/spf-2.0/metadata.mdwn20
1 files changed, 16 insertions, 4 deletions
diff --git a/specs/spf-2.0/metadata.mdwn b/specs/spf-2.0/metadata.mdwn
index 74fdefe..913fd43 100644
--- a/specs/spf-2.0/metadata.mdwn
+++ b/specs/spf-2.0/metadata.mdwn
@@ -107,7 +107,9 @@ and minus signs, and periods. Names must be at least two characters long and
must start with either a letter or a digit. (A regular expression for this is
`[a-z0-9][a-z0-9+.-]+`.)
-Source package names may not begin with the reserved string "src-".
+Source package names may not begin with the reserved string "src-". *This
+limitation is expected to be removed in a future draft of this version of this
+Source Package Format.*
Binary Package Names [bin-name]
-------------------------------
@@ -117,11 +119,14 @@ and minus signs, and periods. Names must be at least two characters long and
must start with either a letter or a digit. (A regular expression for this is
`[a-z0-9][a-z0-9+.-]+`.)
-Binary package names may not begin with the reserved string "src-".
+Binary package names may not begin with the reserved string "src-". *This
+limitation is expected to be removed in a future draft of this version of this
+Source Package Format.*
A binary package clean name is a binary package name with all plus and minus
signs and periods removed. No two binary packages built from the same source
-package may have the same clean name.
+package may have the same clean name. *This limitation is expected to be
+removed in a future draft of this version of this Source Package Format.*
Source Package Version Identifier [src-ver]
@@ -129,7 +134,14 @@ Source Package Version Identifier [src-ver]
In general, the syntax of source package version identifiers is:
- <pkgver>[+sip<siprev>][-<pkgrev>][+<dist>~<distrev>][~bpu<distnum>+<bpurev>]
+ [<epoch>:]<pkgver>[+sip<siprev>][-<pkgrev>][+<dist>~<distrev>][~bpu<distnum>+<bpurev>]
+
+`<epoch>` should almost always be omitted, in which case it is effectively zero.
+It may be used when the upstream version numbering scheme changes or when one or
+more binary packages are migrated to a different source package with a different
+upstream version numbering scheme. It must be a string of one or more digits,
+the first of which must be greater than or equal to `1`. (A regular expression
+for this is `[1-9][0-9]*`.)
`<pkgver>` is the version of the original upstream package or the native
package. It may only consist of lowercase Latin letters, digits, periods,