As of 2.1 openldap defaults to using the "bdb" backend instead of ldbm. Our ebuild turns off bdb, however, if "gdbm" is in USE, which I doubt is what most people will want. As an aside, 2.1.20 is now available. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Hmmm. Also needs to enable crypt in "crypt" is in USE.
In fact, looking at the MDK spec, http://cvs.mandrakesoft.com/cgi-bin/cvsweb.cgi/SPECS/openldap/openldap.spec?rev=1.45&content-type=text/x-cvsweb-markup, there may be a number of things we want to add.
Okay, I'll take these. Closing, since I'm actively working on this issue.