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.

postlfs/shells/zsh.xml

@@ -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>
 
@@ -140,9 +139,11 @@
       commands:
     </para>
 
-<screen><userinput>./configure --prefix=/usr         \
-            --sysconfdir=/etc/zsh \
-            --enable-etcdir=/etc/zsh                  &amp;&amp;
+<screen><userinput>./configure --prefix=/usr            \
+            --sysconfdir=/etc/zsh    \
+            --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>