#34786: cyrus-sasl2 @2.1.25_0 indirectly depends on itself ------------------------------------------+--------------------------------- Reporter: md14-macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Keywords: | Port: cyrus-sasl2 ------------------------------------------+--------------------------------- Changes (by ryandesign@…): * cc: ryandesign@… (added) Comment: Ugh, fantastic... What should we do about that? cyrus-sasl2 @2.1.25 +kerberos linked with libraries provided by the kerberos5 port, so I added the dependency, not realizing the dependency loop. (I wonder why the buildbot didn't tell me about it.) Can we tell cyrus-sasl2 to not do that? If so how, and is there any negative consequence of doing so? -- Ticket URL: <https://trac.macports.org/ticket/34786#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS

#34786: cyrus-sasl2 @2.1.25_0 indirectly depends on itself ------------------------------------------+--------------------------------- Reporter: md14-macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Keywords: | Port: cyrus-sasl2 ------------------------------------------+--------------------------------- Comment(by ricci@…): Replying to [comment:2 md14-macports@…]:

Here are some ideas to break the dependency loop:

1. Patch the cyrus-sasl2 configure script so it will report libraries provided by the kerberos5 port are not present. The effect on the cyrus- sasl2 port will be the same as installing cyrus-sasl2 and kerberos5 from scratch before r94003: cyrus-sasl2 will be built with kerberos support, but not linked with kerberos, because kerberos5 will indirectly depend on cyrus-sasl2, but not vice-versa. 1. Build cyrus-sasl2 without kerberos support. 1. Build gnupg with ldap support disabled. 1. Change kerberos5 to depend on gnupg2 instead of gnupg, and disable ldap support in the gnupg2 configure options. 1. Build openldap without cyrus-sasl support.

I don't know which, if any, of the above would have the least impact.

Personally I'd got with "build gnupg without ldap support" as I expect most users don't use gnupg with LDAP, and that way they're not dragging in the large beast that is OpenLDAP. -- Ticket URL: <https://trac.macports.org/ticket/34786#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS

#34786: cyrus-sasl2 @2.1.25_0 indirectly depends on itself via kerberos5, gnupg, openldap ------------------------------------------+--------------------------------- Reporter: md14-macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Keywords: | Port: cyrus-sasl2 kerberos5 gnupg openldap ------------------------------------------+--------------------------------- Changes (by jmr@…): * port: cyrus-sasl2 => cyrus-sasl2 kerberos5 gnupg openldap -- Ticket URL: <https://trac.macports.org/ticket/34786#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS

#34786: cyrus-sasl2 @2.1.25_0 indirectly depends on itself via kerberos5, gnupg, openldap ------------------------------------------+--------------------------------- Reporter: md14-macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Keywords: | Port: cyrus-sasl2 kerberos5 gnupg openldap ------------------------------------------+--------------------------------- Comment(by ecronin@…): gpg should not be a dependency of kerberos5. It looks like when the port was initially created in r11648 the intent was that MacPorts would verify the detached signature, but that never happened and that code is gone entirely from the Portfile now but the dependency remains... The kerberos source itself doesn't try to verify the signature. -- Ticket URL: <https://trac.macports.org/ticket/34786#comment:9> MacPorts <http://www.macports.org/> Ports system for Mac OS