[MacPorts] #54744: coexistence of libressl, libressl-devel, openssl, boringssl, etc.

[MacPorts]

#54744: coexistence of libressl, libressl-devel, openssl, boringssl, etc.
-------------------------------+----------------------
  Reporter:  ryandesign        |      Owner:  jeremyhu
      Type:  defect            |     Status:  new
  Priority:  Normal            |  Milestone:
 Component:  ports             |    Version:
Resolution:                    |   Keywords:
      Port:  libressl openssl  |
-------------------------------+----------------------

Comment (by jeremyhu):

 Replying to [comment:6 jeremyhu]:
 > > BTW, what do we know about mixing OpenSSL and LibreSSL in the address
 space of a single application, provided that no data is passed between
 implementations? IOW, can a Qt5 application (say, QupZilla) that uses
 OpenSSL via Qt APIs also use non-Qt libraries built to use LibreSSL (say,
 libcurl), or is that just asking for trouble?
 >
 > Should work just fine.  The API isn't objective-c, so the 2 level
 namespace should let things "just work"

 Also, we'e been shipping macOS like this for years with libressl + OpenSSL
 and even longer with multiple versions of OpenSSL.

--
Ticket URL: <https://trac.macports.org/ticket/54744#comment:7>
MacPorts <https://www.macports.org/>
Ports system for macOS