zsh: enable libcap and gdbm

They are already in LFS so there is no significant reason not to use
them.  Using gdbm may cause license issue but AFAIK as long as we don't
edit gdbm or zsh code in a hidden way we'll not violate the license.

And zsh does not use pam_cap (or any PAM module) at all.  Perhaps we
should perform a cleanup on pam_cap dependencies.
This commit is contained in:
Xi Ruoyao 2022-06-11 15:52:51 +08:00
parent 768cf97c5b
commit 4f4e7f18af
No known key found for this signature in database
GPG Key ID: ACAAD20E19E710E3

View File

@ -107,8 +107,7 @@
<bridgehead renderas="sect4">Optional</bridgehead>
<para role="optional">
<xref linkend="libcap-pam"/>,
<xref linkend="pcre"/>, and
<xref linkend="pcre"/> and
<xref linkend="valgrind"/>
</para>
@ -142,7 +141,9 @@
<screen><userinput>./configure --prefix=/usr \
--sysconfdir=/etc/zsh \
--enable-etcdir=/etc/zsh &amp;&amp;
--enable-etcdir=/etc/zsh \
--enable-cap \
--enable-gdbm &amp;&amp;
make &amp;&amp;
makeinfo Doc/zsh.texi --plaintext -o Doc/zsh.txt &amp;&amp;
@ -206,12 +207,12 @@ install -v -m644 Doc/zsh.dvi /usr/share/doc/zsh-&zsh-version;</userinput></scree
</para>
<para>
<option>--enable-cap</option>: This option enables
<parameter>--enable-cap</parameter>: This option enables
POSIX capabilities.
</para>
<para>
<option>--disable-gdbm</option>: This option disables the
<parameter>--enable-gdbm</parameter>: This option enables the
use of the <application>GDBM</application> library.
</para>