Date: Sun, 22 Dec 2013 15:02:54 -0600 From: Scot Hetzel <swhetzel@gmail.com> To: Erick Turnquist <jhujhiti@adjectivism.org> Cc: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Resolving circular dependencies Message-ID: <CACdU%2Bf-TCrOR_vD7%2BBExE7tXtRpV-W7K-wBYnkW2oSg81ky6%2Bw@mail.gmail.com> In-Reply-To: <52B71FD6.5010401@scrubbed.adjectivism.org> References: <52B6352E.4050804@scrubbed.adjectivism.org> <CACdU%2Bf_iGTCzC1q7HUiprz5T4YRLF3n3Zm-ZagP8E=3fKKNvDw@mail.gmail.com> <52B71FD6.5010401@scrubbed.adjectivism.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Dec 22, 2013 at 11:22 AM, Erick Turnquist <jhujhiti@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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACdU%2Bf-TCrOR_vD7%2BBExE7tXtRpV-W7K-wBYnkW2oSg81ky6%2Bw>