Rewrote the GDBM recommendation to be more of a possibility but not endorsed.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@7515 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

chapter06/db.xml

@@ -41,15 +41,19 @@
     <tip>
       <title>Other Installation Possibilities</title>
 
-      <para>There are instructions to build this package in the BLFS
-      book if you need to build the RPC server or additional language
-      bindings. The additional language bindings will require additional
-      packages to be installed. See
-      <ulink url="&blfs-root;view/svn/server/databases.html#db"/> for
-      suggested installation instructions.</para>
-
-      <para>Also, if you would prefer to skip Berkeley DB entirely
-      and use GDBM instead, see the BLFS instructions located at
+      <para>There are instructions to build this package in the BLFS book if you
+      need to build the RPC server or additional language bindings. The
+      additional language bindings will require additional packages to be
+      installed. See <ulink url="&blfs-root;view/svn/server/databases.html#db"/>
+      for suggested installation instructions.</para>
+
+      <para>Also, GDBM <emphasis>could</emphasis> be used in place of Berkeley
+      DB to satisfy Man-DB. However, since Berkeley DB is considered a core part
+      of the LFS build, it will not be listed as a dependency for any package in
+      the BLFS book. Likewise, dozens of hours go into testing LFS with Berkeley
+      DB installed, not with GDBM. If you fully understand the risks versus
+      benefits of using GDBM and wish to use it anyway, see the BLFS
+      instructions located at
       <ulink url="&blfs-root;view/svn/general/gdbm.html"/></para>
       
     </tip>