dev/releases/1/multiarch: Limit scope to dirs.

1 files changed, 16 insertions, 17 deletions

diff --git a/dev/releases/1/multiarch.mdwn b/dev/releases/1/multiarch.mdwn
index 6fefd3a..4da9437 100644
--- a/dev/releases/1/multiarch.mdwn
+++ b/dev/releases/1/multiarch.mdwn
@@ -1,4 +1,4 @@
-[[!meta title="Release Series 1 Goal: Multiarch"]]
+[[!meta title="Release Series 1 Goal: Multiarch Library and Include Directories"]]
 
 A goal for [[release_1.0|dev/releases/1]] is partial multiarch support.
 
@@ -8,31 +8,30 @@ See also the [[multiarch_design_details|dev/multiarch/design]].
 Scope
 =====
 
-It should be possible to manually install packages of specific architectures to
-facilitate cross building and cross installation of packages.  Additionally, all
-packages that provide architecture-dependent files and are to be coinstallable
-should support coinstallation, so that no major changes need to be made to file
-locations to complete the multiarch implementation.  Note that coinstallability
-itself is not a goal for this release series.
+It should be possible to manually install development packages of specific
+architectures to facilitate cross building of packages.  All packages that
+provide architecture-dependent libraries and header files should be
+coinstallable, so that no major changes need to be made to file locations to
+complete the multiarch implementation.  Note that coinstallation support in the
+package manager is not a goal for this release series.
 
 This means that:
 
-  * A filesystem hierarchy with architecture-dependent paths for libraries and
-    executable programs should be designed and documented in the Packaging
-    Policy,
-  * Architecture-dependent files provided by packages that are to be
-    coinstallable should be installed in architecture-dependent locations,
+  * A file system hierarchy with architecture-specific directories for libraries
+    and header files should be designed and documented in the Packaging Policy,
+  * Architecture-dependent libraries and header files provided by packages that
+    are to be coinstallable should be installed in architecture-specific
+    locations,
   * To the extent possible and reasonable, architecture-independent files should
     not be provided by packages that are to be coinstallable,
   * Relevant toolchain packages should be configured and/or patched to use
-    architecture-dependent library paths,
-  * The `PATH` environment variable should be set to contain native-architecture
-    executable program directories, and
-  * opkg should be modified to support `<pkg>:<arch>` names in its `install`
-    command.
+    architecture-specific library and include paths,
 
 Not included in this release goal are:
 
+  * Architecture-specific directories for executables,
+  * Coinstallability of packages providing executable files,
+  * Support in opkg for installing packages built for foreign architectures,
   * Control information to document package coinstallability and
     inter-architecture dependency satisfaction, and
   * Handling of architecture-independent files provided by coinstallable