summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorP. J. McDermott <pjm@nac.net>2013-05-26 10:36:10 (EDT)
committer P. J. McDermott <pjm@nac.net>2013-05-26 10:36:10 (EDT)
commited776291658d5dc95484e69b7bc42cd277ecc65e (patch)
treeb39a47bb5ff1c18f248443760aa5f55e8130d256
parentebb89e8661628527601cc9e97fc496d6e8289568 (diff)
SPF 2.0: Fix ambiguous platconf directory name.
The directory name can consist of a PACKAGE and VERSION or just a PACKAGE. PACKAGE may contain hyphens. Separating PACKAGE and VERSION with a hypen can lead to name collisions. Consider one package named "foo-1.0" and another named "foo". The upstream version of the "foo" package is "1.0". Which package should find its platform configuration files in /usr/share/platconf/PLATFORM/foo-1.0? This is a simple oversight in the specification with so far no major impact on implementations; in fact, opkbuild 3.0 already does this right.
-rw-r--r--specs/spf-2.0/metadata.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/specs/spf-2.0/metadata.mdwn b/specs/spf-2.0/metadata.mdwn
index 1195826..15692cc 100644
--- a/specs/spf-2.0/metadata.mdwn
+++ b/specs/spf-2.0/metadata.mdwn
@@ -81,7 +81,7 @@ Each configuration file must be described with an entry of the following format:
source destination
`source` is the path to the file, relative to the platform configuration
-directory -- either `/usr/share/config/PLATFORM/PACKAGE-VERSION` or
+directory -- either `/usr/share/config/PLATFORM/PACKAGE_VERSION` or
`/usr/share/config/PLATFORM/PACKAGE`, where `PLATFORM` is the architecture
string denoting an application platform, `PACKAGE` is the name of the
configurable source package, and `VERSION` is the upstream version of the