diff options
author | P. J. McDermott <pehjota> | 2012-07-19 01:25:44 (EDT) |
---|---|---|
committer | P. J. McDermott <pjm@nac.net> | 2012-07-19 01:25:44 (EDT) |
commit | 1396cdf3e42b356bed653d6bfa472b10562ad4cf (patch) | |
tree | 9f4c2c7b3e0c3ee93ff2baefe176fe5f08f6c597 /dev/releases | |
parent | 47bee39909a0047ee1b4b2f5c52d983653015ee2 (diff) |
Document multiarch release goal scope.
Diffstat (limited to 'dev/releases')
-rw-r--r-- | dev/releases/1/multiarch.mdwn | 36 |
1 files changed, 36 insertions, 0 deletions
diff --git a/dev/releases/1/multiarch.mdwn b/dev/releases/1/multiarch.mdwn new file mode 100644 index 0000000..7dcf278 --- /dev/null +++ b/dev/releases/1/multiarch.mdwn @@ -0,0 +1,36 @@ +[[!meta title="Release Series 1 Multiarch Release Goal"]] + +A goal for release 1.0.0 is partial multiarch support. + + +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. + +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, + * 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, and + * The `PATH` environment variable should be set to contain native-architecture + executable program directories. + +Not included in this release goal are: + + * Control information to document package coinstallability and + inter-architecture dependency satisfaction or + * Handling of architecture-independent files provided by coinstallable + architecture-dependent packages or other coinstallability considerations in + package management. |