Randy McMurchy wrote: > I suppose the question at hand is should CrackLib be recommended?
In the BLFS section Notes On Building Software is written: > * Required means that the target package cannot be correctly built > without the dependency having first been installed. => CrackLib is not required > * Recommended means that BLFS strongly suggests this package is > installed first for a clean and trouble-free build, that won't have > issues either during the build process, or at run-time. It wouldn't have issues without CrackLib and it definitely will be trouble-free. => CrackLib is not recommended > * Optional means that this package might be installed for added > functionality. Often BLFS will describe the dependency to explain the > added functionality that will result. It does add functionality. => *CrackLib is optional*. That is my opinion. - Mordae -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
