On Tuesday November 10 2015 04:46:50 Ryan Schmidt wrote: > > No, but if the ABIs are indeed not compatible there is no other solution, > > is there? > > What has currently be done with libressl in MacPorts is a bug, not a solution.
?? Why? It leaves the educated user with a choice regardless of which of openssl or libressl is the default/preferred flavour. That is always a good thing IMHO. > It might be better to take the choice away from the user and just make a > decision that we want libressl to be our default ssl library in MacPorts. > Change the libressl and openssl ports so that they do not conflict, but > rather install in different locations. You think that won't impose extra effort on port maintainers? It seems *ssl is expected to be found via pkgconfig; as long as dependent ports aren't all written to search for either libressl or openssl (and the projects themselves modified to support parallel installation OOTB) you're still going to have the need for libssl.pc and libcrypto.pc files. Those must either be in the "global" pkgconfig directory, or else you'll need to use `configure.env` to point to the dedicated pkgconfig dir of current choice, which means introducing and maintaining a PortGroup. What would the argument be to switch MacPorts to use libressl by default? @Brandon: > See the Gentoo dev link given previously Care to repeat it, I cannot seem to find it in this thread? R. _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
