Hi, I've been thinking about the implications of alternative/drop-in replacement ports and ABI differences.
IIUC, libressl and openssl are API-compatible alternatives that do not build to ABI-compatible libraries. Yet I have noticed that ports use a path:-style dependency declaration which allows users to chose to install either the one or the other. Is there anything currently in MacPorts that avoids issues that will probably arise when you install libressl and then pull in a prebuilt binary that will supposedly be built against openssl? Idem for the classical use of path:-style dependency declarations where they allow to install a -devel port. The standard and -devel port may not provide a 100% compatible ABI; is it purely up to the port maintainer to ensure that this never leads to issues with binary builds (and for the user's responsibility if it does)? R.
