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.

0 files changed, 0 insertions, 0 deletions