[MacPorts] #51516: MacPorts should use a bundled copy of a newer libcurl and SSL library rather than the OS X version

[MacPorts]

#51516: MacPorts should use a bundled copy of a newer libcurl and SSL library
rather than the OS X version
--------------------------+--------------------------------
  Reporter:  ryandesign   |      Owner:  macports-tickets@…
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:  MacPorts Future
 Component:  base         |    Version:
Resolution:               |   Keywords:
      Port:               |
--------------------------+--------------------------------

Comment (by RJVB):

 Same tests performed on Linux too now, IMHO confirming the validity of the
 underlying ideas I used.

 I could start working on filtering out my own tweaks and a non-devel `port
 :MacPorts-pextlib` to put in a PR (preferably a single one, possibly with
 several commits) but I'd like to have some feedback first. Esp. about the
 idea of using a new, co-installable libressl subport (IMHO not a bad
 option to have anyway) and `port:MacPorts-libcurl`.

 Reading https://www.libressl.org/goals.html and comparing the
 port:openssl3 and port:libressl Portfiles only strengthens my idea that
 LibreSSL is a good choice for MacPorts's own SSL backend (one originating
 on another BSD derivative, even) but I have no hard arguments against
 OpenSSL if the new Pextlib will use the corresponding libcrypto anyway.

 Regarding curl: I mentioned the possibility to keep `port:MacPorts-
 libcurl` on the previous rather than the current release. I didn't yet
 implement that to keep the subport as simple as possible so I'll have to
 make the necessary modifications if it is deemed wise to impose a time
 buffer for testing a new curl release "in the wild" and beyond a simple
 `port -v test MacPorts-libcurl`.

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