On 11/24/2018 03:38 AM, Pierre Labastie via blfs-support wrote:
Now, you do not have always to rebuild a package, even if there is an optional dependency: it depends on whether you want the functionality added by the circular dependency. For example, I've never built libtirpc before Linux-PAM, because I do not need the added functionality (I don't even know what it is, actually :).
libtirpc is needed for nfs via rpcbind and nfs-utils. The other packages that use this capability are mostly related to that: samba, lsof, autofs, dovecot, etc.
If you don't use remotely mounted file systems, then libtirpc is not needed unless the package requires it (autofs, lsof, libnsl).
For any package, optional means that the user should know what additional capabilities are provided by the optional dependency and only build that if that capability is desired.
Of course, sometimes knowing if the capability is needed is not easily known so many users will default to building everything.
Of course, as editors, we generally build most packages if not everything, even if we don't use a lot of the packages.
-- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
