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

 Replying to [comment:44 ryandesign]:
 > Yes, I know that merely using a bundled curl that's still linked with
 the system's openssl will not solve all of the problems being discussed in
 this ticket. But I think we should still do it because it will solve some
 of the problems (e.g. comment:30).

 I think we all agree that we should not bundle an SSL library with
 MacPorts.

 Now that the mirroring is fixed, I'm wondering whether we should just
 close this ticket as wontfix. You mentioned that you want a bundled
 libcurl in MacPorts for other reasons, but the cosmetic issue you linked
 in #51045 does in my opinion not warrant the additional effort of bundling
 libcurl (especially since it's fixed since two OS releases and we could
 add a simple workaround in base for that).

 Do you have any other reasons for bundling a libcurl? If not, I would
 close this ticket as wontfix.

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