As an example, Juniper Networks needs openldap-sasl-client in order to authenticate on our FreeBSD build systems. But openldap-client is a dependacy for a LARGE number of other ports we need to use.
The 'ldd' difference that SASL support adds is only:
libldap-2.4.so.2 => /usr/local/lib/libldap-2.4.so.2
liblber-2.4.so.2 => /usr/local/lib/liblber-2.4.so.2
+ libsasl2.so.3 => /usr/local/lib/libsasl2.so.3
libssl.so.111 => /usr/lib/libssl.so.111
libcrypto.so.111 => /lib/libcrypto.so.111
libc.so.7 => /lib/libc.so.7
+ libdl.so.1 => /usr/lib/libdl.so.1
libthr.so.3 => /lib/libthr.so.3
I do not see this as a burden given the LARGE number of dependancies most of our other ports have grown in the last decade as every knob of functionality seems turned on in many.
SASL support should be the default for openldap-client given it is so low cost, but the cost of having to build 1000 packages from source is a high burden on an organization.
*** This bug has been marked as a duplicate of bug 257374 ***