break up cyclic dependency openldap21 <-> cyrus-sasl2

[Guy Middleton]

On Wed, Apr 09, 2003 at 11:56:05AM +0200, Oliver Eikemeier wrote:
> Christian Kratzer wrote:
> >>
> >>I'm trying to enable OpenLDAP 2.1 SASL support. It is easy to patch
> >>net/openldap21 and security/cyrus-sasl2 so that they compile with each
> >>other, but then I've got a cyclic dependency cyrus-sasl-2.1.12 ->
> >>openldap21-2.1.16 -> cyrus-sasl-2.1.12. Obvioulsy portupgrade doesn't
> >>like cyclic dependencies. FreeBSD Porter's Handbook
> >><http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/>
> >>does not mention this, so I am stuck.
> > 
> > one more point. Openldap >= 2.1.13 breaks cyrus-sasl2 because of api
> > changes.  I have mailed the cyrus-sasl2 maintainer with patches
> > that address this and other points.
> > 
> > I will send a pr later today to address this.
> 
> The patches are already in the cyrus CVS, you just have to remove ldap 
> caching from saslauthd/lak.[ch], but I think we have to address the 
> dependency problem too. Splitting up cyrus-sasl and the saslauthd looks 
> like a good plan to me, and the you have to do the patches on saslauthd.

I just ran into the same problem myself -- I would like to compile OpenLDAP
with SASL support, and I don't really need saslauthd, so the direction of
dependency in the ports collection is backwards for me.

 -Guy Middleton