[MacPorts] #69490: libressl cannot be installed when it depends on a clang port because it conflicts with openssl

[MacPorts]

#69490: libressl cannot be installed when it depends on a clang port because it
conflicts with openssl
-------------------------+----------------------
  Reporter:  ryandesign  |      Owner:  artkiver
      Type:  defect      |     Status:  assigned
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:              |   Keywords:
      Port:  libressl    |
-------------------------+----------------------

Comment (by artkiver):

 Thanks for bringing this to my attention!

 It looks similar to https://trac.macports.org/ticket/68811 which had
 somehow slipped from my awareness until earlier this week.

 I had locally experimented with modifying the net/wget Portfile to use the
 path:lib/libssl.dylib:libressl instead of the OpenSSL PortGroup and it
 seemed to function OK, but I never submitted that as a PR.

 I am guessing, curl in my use case is a little different since that
 appears to be dependent upon which variant is installed?

 e.g. from the net/curl Portfile:

 {{{
     variant ssl conflicts darwinssl gnutls mbedtls wolfssl description
 {Allow se
 cure connections using OpenSSL} {
         depends_lib-append      path:lib/libssl.dylib:openssl \
                                 path:share/curl/curl-ca-bundle.crt:curl-
 ca-bundle
         configure.args-delete   --without-ssl
         configure.args-replace  --without-openssl --with-openssl
         configure.args-append   --with-ca-bundle=${prefix}/share/curl
 /curl-ca-bundle.crt
     }
 }}}

 I admit, I am a little bit over my head with some of this stuff. I had
 been thinking of doing a TLS library audit of Portfiles and making
 assiduous use of the path:lib/libssl.dylib:openssl methodology wherever
 possible, but I haven't even managed to get a local build of mpbb working
 correctly yet. I did recently upgrade the SSD on one of my systems so I
 should at least have some more storage space with which to work, but my
 resources (not just computationally, but also financially and in terms of
 having peace and quiet and space to myself) are extremely constrained,
 which is why I tend to leave openmaintainer in place on any MacPort where
 I am also a comaintainer, so I welcome any suggestions, help or PRs as
 well!

 Not to dismiss this in the slightest, I wish I were able to rectify it
 more quickly.

 As a first guess: do you think that ameliorating the curl dependencies to
 be a bit more LibreSSL friendly/preferential might improve the situation?
 I do have some laptops with older versions of OS X but most of them are in
 storage and not too easy for me to get to for testing personally at the
 moment.

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