| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
With SPF 2.0 we're standardizing on the string "platconf" (rather than the old
"config") to refer to platform configurations.
opkbuild 3.0 already uses the new string.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
Slashes can't be used in version IDs because they aren't allowed in
filenames in most/all filesystems.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
Omitted (at least temporarily) are "Packaging Recommendations" and
"Example Files".
|