summaryrefslogtreecommitdiffstats
path: root/dev/pkg/opkg
diff options
context:
space:
mode:
Diffstat (limited to 'dev/pkg/opkg')
-rw-r--r--dev/pkg/opkg/static.mdwn14
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
==========