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

 Replying to [comment:112 ryandesign]:
 > Replying to [comment:111 RJVB]:
 > You can easily download for example the 4.170.0_10 and 4.170.0_11
 packages from https://packages.macports.org/p5.34-www-curl/ and extract
 and compare their contents to convince yourself that they are different.

 I simply said I couldn't determine the reason why that port is special,
 and of course meant from the remarks in the portfile(s). But yes, it
 stands to reason that curl bindings for a scripting language need to be
 updated to include the latest functionality (I should probably have
 realised that was the likely case here).

 > We don't want you to waste your time developing changes if they would
 not be accepted. (I'm not saying that is necessarily the case here.)

 Truth is that it wouldn't exactly be a waste of my time to do something I
 don't hate doing and of which I'll reap the benefits myself. I wouldn't be
 jammering about this topic here if that weren't the case!

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