diff options
author | Patrick McDermott <pehjota> | 2017-08-07 14:08:34 (EDT) |
---|---|---|
committer | Patrick McDermott <pehjota> | 2017-08-07 14:08:34 (EDT) |
commit | 782a1859e311c027f172a5c1d3cc13cc73f04b91 (patch) | |
tree | e55987a23047b8a37e54e8044a90e0dd7bb97047 | |
parent | 2aa66ceff5b28c197e2ef04bab71f03e0f34a71b (diff) |
dev/pkg/opkg/static: Add "an additional package with"
-rw-r--r-- | dev/pkg/opkg/static.mdwn | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/dev/pkg/opkg/static.mdwn b/dev/pkg/opkg/static.mdwn index 62c733f..a81e810 100644 --- a/dev/pkg/opkg/static.mdwn +++ b/dev/pkg/opkg/static.mdwn @@ -56,13 +56,13 @@ Option 3 A compromise between options 1 and 2 is to leave the `libopkg.1` and `libopkg.1-dev` binary packages as they are and statically link the `opkg` -executable in the `opkg` package with libopkg, without building an `opkg` -executable that dynamically links against libopkg. This means duplicated code -and some increase in file system usage on any platforms that may someday include -some other libopkg-using application in the future. But it also minimizes file -system usage on platforms where opkg is the only user of libopkg, like option 1, -and balances package archive size between options 1 and 2 (and has the same -package feed index file sizes as option 1). +executable in the `opkg` package with libopkg, without building an additional +package with an `opkg` executable that dynamically links against libopkg. This +means duplicated code and some increase in file system usage on any platforms +that may someday include some other libopkg-using application in the future. +But it also minimizes file system usage on platforms where opkg is the only user +of libopkg, like option 1, and balances package archive size between options 1 +and 2 (and has the same package feed index file sizes as option 1). Conclusion ========== |