On Sun, Dec 22, 2013 at 11:22 AM, Erick Turnquist <jhujh...@adjectivism.org> wrote: > On 2013-12-22 09:51, Scot Hetzel wrote: >> >> The best way to solve this would be to create 3 ports that would >> create the appropriate gssapi mech: >> >> security/cyrus-sasl2-mech-gssapi-base <- Kerberos Support from >> /usr/lib/libkrb5.a >> security/cyrus-sasl2-mech-gssapi-krb5 (slave port) >> security/cyrus-sasl2-mech-gssapi-hemidal (slave port) > > > What would the exact dependencies be in this case? I feel like I've missed > something important, because both openldap24-sasl-client and cyrus-sasl2 > still actually depend on the MIT Kerberos libraries, would we not end up > with a circle of four packages instead of three? > > Before: > openldap24-sasl-client -> cyrus-sasl2 -> krb5 -> openldap24-sasl-client > > After: > openldap24-sasl-client -> cyrus-sasl2 -> cyrus-sasl2-mech-gssapi-krb5 -> > krb5 -> openldap24-sasl-client
The dependencies should be: krb5 -> openldap24-sasl-client -> cyrus-sasl2 cyrus-sasl2-mech-gssapi-krb5 -> krb5 The cyrus-sasl2-mech-gssapi-krb5 should be the only one depending on the MIT Kerberos Libraries. -- DISCLAIMER: No electrons were maimed while sending this message. Only slightly bruised. _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"