On 01/11/2014 10:02 AM, Pierre Labastie wrote: > > I'd like to know when instructions for optional features should be given, and > when deemed such, why they should not be moved to recommended instructions.
The way I see it, recommended classification should be used for: 1) dependencies that require explicit switch to disable at compile time 2) system-installed dependencies which can be used instead of bundled ones 3) dependencies that add a feature that is required to build some other package in the book Everything else is either required or optional. There is nothing wrong with listing and explaining optional dependencies in detail or fixing packages to build with some optional feature. -- "LEGO won't be ready for the average user until it comes pre-assembled, in a single unified look, and glued together so it doesn't come apart." -- Iranon -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
