Some libraries (like berkdb and gdbm) are used by openldap only at server side. Ebuild does not take it into account and depends on berkdb even when neither 'berkdb' nor 'gdbm' is in USE flags. I would propose wrapping dependency conditions for berkdb/gdbm inside minimal? () block or splitting the ebuild into -client and -server as these parts are semantically different things (see discussion for bug #143473).
No plans to split anything here.
Due to not splitting things out this won't change. Won't fix sorry.
I proposed two possible solutions. While I understand that the second one (package split) may not be what you want, the first one was to actually fix USE flag minimum by wrapping berkdb/gdbm dependency inside !minimal? () block like this: --- openldap-2.3.24-r1.ebuild 2006-09-18 15:53:55.000000000 +0200 +++ openldap-2.3.24-r1.ebuild 2006-09-18 15:58:59.000000000 +0200 @@ -29,10 +29,12 @@ perl? ( >=dev-lang/perl-5.6 ) samba? ( >=dev-libs/openssl-0.9.6 ) kerberos? ( virtual/krb5 ) - berkdb? ( ${RDEPEND_BERKDB} ) - !berkdb? ( - gdbm? ( >=sys-libs/gdbm-1.8.0 ) - !gdbm? ( ${RDEPEND_BERKDB} ) + !minimal? ( + berkdb? ( ${RDEPEND_BERKDB} ) + !berkdb? ( + gdbm? ( >=sys-libs/gdbm-1.8.0 ) + !gdbm? ( ${RDEPEND_BERKDB} ) + ) ) selinux? ( sec-policy/selinux-openldap )"
ok, I see what there is to gain here, and I'm implementing it for 2.3.27-r1 ;-). If we build with USE=minimal, we're bringing a whack of DEPs that we don't actually need.
fixed in cvs.
