diff options
| author | P. J. McDermott <pehjota> | 2012-07-19 01:30:37 (EDT) |
|---|---|---|
| committer | P. J. McDermott <pjm@nac.net> | 2012-07-19 01:30:37 (EDT) |
| commit | 01b16826a6558517924e93b7be9271bb6c9e65e4 (patch) | |
| tree | 69ca54d14b2483072ffe41b90a5856dbf2459f57 /dev/multiarch | |
| parent | 1396cdf3e42b356bed653d6bfa472b10562ad4cf (diff) | |
Fix formatting issues in MA design document.
Diffstat (limited to 'dev/multiarch')
| -rw-r--r-- | dev/multiarch/design.mdwn | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/dev/multiarch/design.mdwn b/dev/multiarch/design.mdwn index d1a28e3..e18aa46 100644 --- a/dev/multiarch/design.mdwn +++ b/dev/multiarch/design.mdwn @@ -129,32 +129,32 @@ During build-time, there are two possible architectures for any dependent packag * Host-architecture (architecture for which packages are built). Packages for this architecture provide things like libraries and headers. An example is - libexpat.1-dev. + `libexpat.1-dev`. * Build-architecture (architecture on which packages are built). Packages for - this architecture provide things like build utilities An example is - pkg-config. + this architecture provide things like build utilities. An example is + `pkg-config`. During install-time, there are also two possible architectures for any dependent package: * Host-architecture (architecture for which packages are installed). Packages for this architecture provide things like libraries and utilities. Examples - include libz.1, gcc-4.7-<arch> (dependency of gcc-<arch>), and fakeroot - (recommendation of opkhelper-1.0). + include `libz.1`, `gcc-4.7-<arch>` (dependency of `gcc-<arch>`), and + `fakeroot` (recommendation of `opkhelper-1.0`). * Install-architecture (architecture on which packages are installed). Packages for this architecture provide things like utilities used by - maintainer scripts. An example is insserv (or a similar tool). + maintainer scripts. An example is `insserv` (or a similar tool). Host-architecture packages should be coinstallable with themselves, and they should satisfy dependencies of the same architecture. For example, the -dependency of libexpat.1-dev:cortexa8-linux-eglibc on libexpat.1 should resolve -to a dependency on libexpat.1:cortexa8-linux-eglibc. +dependency of `libexpat.1-dev:cortexa8-linux-eglibc` on `libexpat.1` should +resolve to a dependency on `libexpat.1:cortexa8-linux-eglibc`. Build- and install-architecture packages need not be coinstallable with themselves, and they should satisfy dependencies of any architecture. For -example, the build dependency of glib (built on core-linux-eglibc for -cortexa8-linux-eglibc) on pkg-config should resolve to a build dependency on -pkg-config:core-linux-eglibc. +example, the build dependency of `glib` (built on `core-linux-eglibc` for +`cortexa8-linux-eglibc`) on `pkg-config` should resolve to a build dependency on +`pkg-config:core-linux-eglibc`. Debian and Ubuntu specify such properties in a `Multi-Arch` control field. A value of `same` indicates that a package satisfies dependencies of the same |