system/execline: Updated for version 2.5.3.0.

Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>

1 files changed, 23 insertions, 3 deletions

diff --git a/system/execline/README b/system/execline/README
index 567b32fdb902e..c3019a5055b95 100644
--- a/system/execline/README
+++ b/system/execline/README
@@ -1,4 +1,4 @@
-execline is a (non-interactive) scripting language, like sh ; but its
+execline is a (non-interactive) scripting language, like sh; but its
 syntax is quite different from a traditional shell syntax. The
 execlineb program is meant to be used as an interpreter for a text
 file; the other commands are essentially useful inside an execlineb
@@ -9,6 +9,26 @@ getopt-style option handling, filename globbing, and more. Meanwhile,
 its syntax is far more logic and predictable than the shell's syntax,
 and has no security issues.
 
-execline requires skalibs at build time but not at run time.
+NOTE:
+Upstream recommends building skarnet.org softwares with static libraries
+as most of skarnet.org softwares are small enough that using shared
+libraries are generally not worth using. Therefore, by default, shared
+libraries are not built and binaries are linked against the static
+versions of the skarnet.org libraries.
 
-execline installs into /command to match the skarnet.org examples.
+If you want to also build the shared libraries, pass BUILD_SHARED=yes
+environment variable to the SlackBuild script like below:
+
+    BUILD_SHARED=yes ./execline.SlackBuild
+
+Similarly, to avoid building the static libraries, you can pass
+BUILD_STATIC=no to the script. For example, to only build the shared
+libraries and not the static ones, you can do something like:
+
+    BUILD_SHARED=yes BUILD_STATIC=no ./execline.SlackBuild
+
+If you just want to build and use skarnet.org softwares, building only
+the static libraries should be sufficient.
+
+If you want the binaries to be linked against the shared versions of the
+skarnet.org libraries, pass LINK_SHARED=yes to the script.