diff options
| -rw-r--r-- | specs/source-package-format-2.0.txt | 16 |
1 files changed, 2 insertions, 14 deletions
diff --git a/specs/source-package-format-2.0.txt b/specs/source-package-format-2.0.txt index 05645df..2b72f90 100644 --- a/specs/source-package-format-2.0.txt +++ b/specs/source-package-format-2.0.txt @@ -56,6 +56,8 @@ source package format: - The user can choose to build all binary packages, only architecture-independent binary packages, or only architecture-independent binary packages. See section 5 for rationale behind this design. + * The source package version is no longer included in `control`. + - It is already given in the most recent entry in `changelog`. 5. Rationale @@ -428,20 +430,6 @@ The fields in the source package metadata are: must be at least two characters long and must start with either a letter or a digit. - * `Version` (required) - The version number of the package. The format is: - - <upstream_version>[-<package_revision>] - - `<upstream_version>` is the version of the original upstream package, if - any. - - `<package_revision>` is the version of the distribution packaging. It is - optional and should be omitted for native packages. It should be - incremented for each uploaded revision of packaging for the same upstream - package version. It should be reset for the first uploaded revision of - packaging for a new upstream package version. - * `Maintainer` (required) The name and e-mail address of the package maintainer. This field must follow the syntax of the `mailbox` symbol in RFC 5322 section 3.4. |