kerberos5 and fbopenssl provide /opt/local/include/gssapi.h, making them mutually exclusive

[hinnerk (Hinnerk Haardt)]

Both kerberos5 and fbopenssl provide /opt/local/include/gssapi.h making them and all depending ports mutually exclusive. (Software version info below.)

# port install kerberos5
[…]
# port install fbopenssl
--->  Computing dependencies for fbopenssl
--->  Activating fbopenssl @0.0.4_2
Error: Target org.macports.activate returned: Image error:\
/opt/local/include/gssapi.h is being used by the active\
kerberos5 port.  Please deactivate this port first, or \
use 'port -f activate fbopenssl' to force the activation.
Log for fbopenssl is at: /opt/local/var/macports/logs/\
_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_fbopenssl/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

A sample of now mutually exclusive packets are cyrus-sasl2 (depends on kerberos5, see #23812) and curl with +spnego (depends on fbopenssl)

Software Versions

• kerberos5: @1.7.1
• fbopenssl: @0.0.4 rev 2
• MacPorts 1.9.1
• Max OS X 10.6.4
• Xcode 3.2.2

[ryandesign (Ryan Carsten Schmidt)]

kerberos5 and fbopenssl both have no maintainer, so if anybody has a suggestion for how this should be handled, please let us know, or ideally supply a patch.

[ryandesign (Ryan Carsten Schmidt)]

For now, I marked the ports as conflicting in r70017.

[vikingjs@…]

I'm willing to take a shot at a patch, but I'm somewhat out of my depth. Would renaming fbopenssl's version of gssapi.h to fbgssapi.h and to change all references in the source code be a valid solution?

[vikingjs@…]

Hm.. on further reflection I realize that I don't know who consumes that header, and that's going to cause trouble. So I guess I answered my own question.