If someone installs dev-libs/cyrus-sasl with ldap support to authenticate with a remote ldap server, the ebuild will enable ldap and ldapdb. ldapdb is not needed for ldap authentication, and generates the following error on every connection (which in my case is several thousand times per day): _sasl_plugin_load failed on sasl_auxprop_plug_init for plugin: ldapdb Since I'm not an expert on dev-libs/cyrus-sasl, I have modified the ebuilds to separate ldapdb and ldap support by adding a ldapdb use flag. This will allow people to enable the ldapdb plugin if they really need it, while not clogging the logs when it's not needed. You can accomplish the same thing by removing the ldapdb plugin from /usr/lib/sasl2, but I would rather have the ebuild not put it there in the first place. Reproducible: Always
Created attachment 232369 [details, diff] Patch to add ldapdb use flag to current dev-libs/cyrus-sasl stable ebuilds
Fixed in CVS in cyrus-sasl-2.1.25.
