diff options
| author | P. J. McDermott <pjm@nac.net> | 2012-03-08 12:07:01 (EST) |
|---|---|---|
| committer | P. J. McDermott <pjm@nac.net> | 2012-03-08 12:07:01 (EST) |
| commit | 6d4f772de655b1dc1d9a7a05a122ec871bfd1af4 (patch) | |
| tree | 8e60249148b8e199f88e131de7d7db7cda23c302 | |
| parent | 1e5971a73338042cabe6add480fbec9f9ab1de72 (diff) | |
Clarify use of 'Architecture' field values.
| -rw-r--r-- | specs/source-package-format-1.0.txt | 9 |
1 files changed, 7 insertions, 2 deletions
diff --git a/specs/source-package-format-1.0.txt b/specs/source-package-format-1.0.txt index 63d5db4..616216f 100644 --- a/specs/source-package-format-1.0.txt +++ b/specs/source-package-format-1.0.txt @@ -288,9 +288,14 @@ The fields in the binary package metadata are: - The string `all` to specify that the package can be built on any binary architecture and any application platform and can then be installed on binary architectures and/or application platforms other than those on - which it is built. + which it is built. This value should be used for packages that provide + only architecture- and platform-independent files, such as common shell + scripts or data. - The string `any` to specify that the package can be built for any binary - architecture and any application platform. + architecture and any application platform. This value should be used + for packages that provide architecture- and/or platform-dependent files + that can be built and run on any architecture and platform, such as + portably-written C programs. * `Essential` (optional) A flag to indicate whether the package is essential for the functioning of a |