Rewrite paragraph on configuration packages.

The language may not be very clear, but its the most precise way I can
imagine to describe this fairly advanced topic in software package
management.

1 files changed, 12 insertions, 6 deletions

diff --git a/package-application-configuration.txt b/package-application-configuration.txt
index 23d0834..6e15188 100644
--- a/package-application-configuration.txt
+++ b/package-application-configuration.txt
@@ -66,12 +66,18 @@ architecture.
 CONFIGURATION PACKAGES
 ======================
 
-For each configurable software package and for each of its supported application
-platforms, there will be exactly one "configuration" binary package.  This
-configuration package will have a name of the form "<pkgname>-config", where
-"<pkgname>" is the name of the configurable source package.  The configuration
-package will install into "/usr/share/config/<pkgname>" any configuration files
-needed by the configurable package at build time or install time.
+For each configurable software package, there will be exactly one virtual
+"configuration" binary package.  For each configurable software package and for
+each of its supported application platforms, there will be exactly one real
+"configuration" binary package that provides the configurable software package's
+virtual configuration package.  The virtual configuration package will have a
+name of the form "<pkgname>-config", where "<pkgname>" is the name of the
+configurable source package.  The application platform-specific configuration
+package will have a name of the form "<pkgname>-config-<appname>", where
+"<appname>" is the name of the application platform architecture.  The
+application platform-specific configuration package will install into
+"/usr/share/config/<appname>/<pkgname>" any configuration files needed by the
+configurable package at build time or install time.
 
 
 PACKAGE BUILDING