diff options
| author | Patrick McDermott <pehjota> | 2020-06-12 07:57:24 (EDT) |
|---|---|---|
| committer | Patrick McDermott <pehjota> | 2020-06-20 17:08:05 (EDT) |
| commit | 5069c060556a05a7b4868ff2da5b207d2a4fa64c (patch) | |
| tree | f535c45ff067b262c8ae237747709aa9ccdf4ec8 | |
| parent | 259d570e5889e9926fa8001031b992bb728b1b80 (diff) | |
[WIP] dev/multiarch/design: Document sections idea
| -rw-r--r-- | dev/multiarch/design.mdwn | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/dev/multiarch/design.mdwn b/dev/multiarch/design.mdwn index 4d2ad15..6ed3a95 100644 --- a/dev/multiarch/design.mdwn +++ b/dev/multiarch/design.mdwn @@ -187,6 +187,19 @@ Special design considerations need to be given to install-time dependencies. Specific use case analysis can help here. +Section-Based Solution +---------------------- + +A way to avoid having to modify opkg is to separate packages into archive +sections by package type, e.g.: `bin`, `lib`, `dev`, `dbg`, and `share`. +opkbuild could possibly automatically generate a correct `Section` control field +by package name for many packages. + +prokit would add feed lists for the native-architecture `bin` and `lib` +sections, and users would have to enable other feed lists themselves (e.g. to +add a foreign architecture's `lib` and `dev` feeds to cross-build packages. + + Architecture-Independent Files ============================== |