Ken Moffat wrote:
My preference is recommended, if possible. But agree with Ken's decision
if he still wishes to promote to required
My rationale is that Recommended either means
(i.) The package can build without this, and without extra configure
switches, but the recommended package provides useful extra
functionality (is that a word ?)
or
(ii.) The package can be built without this, but you need to supply
extra configure switches.
This package, as shipped, matches neither option. I am reluctant to
include a patch in the book just so that people can detune what
upstream shipped.
My definition of recommended is that the package provides extra
functionality for the package that you probably want. The instructions
provided also assume that all recommended packages are installed. If you
don't want to install a recommended dependency, then there may be other
things that you need to do to build the package. Those things may
include, but are not limited to, a modification of options for configure.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
