Chris Staub wrote:
Yes, I am asking if there is a reason for it. The main reason I'm asking
is because there are several other packages that stated "Berkeley DB OR
GDBM" but Berkeley was still commented out - why was it left in these
few packages?
Hmmm, maybe I just answered my own question...looks like it was
commented out wherever it was listed as "optional"...duh...
Although, it is possible that it could be reworded...maybe since those
packages that require "a database" (choice between Berkeley and GDBM),
and Berkeley DB is assumed to have been installed in LFS, that means the
requirement is already fulfilled, Berkeley could be removed from the
"Required" list and GDBM could be moved to "Optional". Just my opinion. :)
I guess one reason for the potential confusion is that there just isn't
precedent (that I know of) for this kind of situation, where a package
in LFS is listed in dependencies for other BLFS packages as one of
several options.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
