summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPatrick McDermott <pehjota>2020-06-21 10:32:43 (EDT)
committer Patrick McDermott <pehjota>2020-06-21 10:32:43 (EDT)
commit921067e5e3a1962dd751bac8c5042f28671b4be8 (patch)
tree6768f73ccbfcc36f974fa951c20a5d4ac8b3d9d7
parent8421b6d86b7fa6afd9670049f1a531909905f2cf (diff)
dev/multiarch: Clarify dep semantics direction
-rw-r--r--dev/multiarch.mdwn3
1 files changed, 2 insertions, 1 deletions
diff --git a/dev/multiarch.mdwn b/dev/multiarch.mdwn
index 5315e76..d7c6a05 100644
--- a/dev/multiarch.mdwn
+++ b/dev/multiarch.mdwn
@@ -85,7 +85,8 @@ provides: executables and/or libraries). Again this requires modifications to
the package manager to affect dependency resolution. ProteanOS's design is
similar, but implemented in a way such that *dependent* binary packages are
responsible for declaring the architectures of *their dependencies* (which can
-be done automatically at build time).
+be done automatically at build time, so package maintainers can focus on
+declaring how their packages satisfy dependencies, as in Debian and Ubuntu).
One way to declare dependency semantics is by introducing a new single-purpose
control field like Debian's and Ubuntu's `Multi-Arch`. However, ProteanOS will