[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):

 Come to think of it ... before my current hack I used a
 `DYLD_LIBRARY_PATH` and/or `DYLD_INSERT_LIBRARIES` (and their Linux
 equivalents) to overload the system libcurl with the one from MacPorts.
 That was tricky because of how MacPorts controls the environment and
 because of the side-effects `DYLD_LIBRARY_PATH` can have.

 I *think* a rewrite of `curl.c` can be avoided if we can simply try to
 `dlopen` an appropriate (tested etc) libcurl from the `port` driver
 command before it loads the Pextlib extension. It looks like this would
 require either a glue library that provides at least a stub Tcl package
 loader function (`Curl_Init()`) or else adding a Tcl extension
 (https://wiki.tcl-lang.org/page/dlopen+extension).

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