[MacPorts] #70127: Using a newer libcurl from "base"

[MacPorts]

#70127: Using a newer libcurl from "base"
--------------------------+--------------------
  Reporter:  RJVB         |      Owner:  (none)
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  base         |    Version:
Resolution:               |   Keywords:
      Port:               |
--------------------------+--------------------

Comment (by RJVB):

 Replying to [comment:2 ryandesign]:
 > #51516

 Weird, I did do a search on tickets by me containing "curl" ...Replying to
 [comment:3 kencu]:
 > much easier to bootstrap:

 My hack is actually dead simple too (on Mac), so much so that I haven't
 even written a script for it. You just need to remember doing it. How to
 bootstrap an update to Pextlib's `libcurl` does take some thinking out,
 probably, that's clear.
 I haven't looked at your repo, but what SSL provider does your minimal
 curl use? The system one uses Apple's own SSL framework, which is
 undoubtedly the reason why it no longer suffices. Building a newer curl
 version against that same framework would probably not help very much.

 Thinking over the idea of a `port:curl` subport again I think that's not
 even needed. `port:curl` could simply have a `post-activate` that installs
 a copy of the actual `libcurl` binary in the designated location, doing
 this only for curl versions that have been verified to work against "base"
 built on the current host. With luck that will cover the majority of
 supported OS versions and on those a `port -n install curl +gnutls` could
 be the first thing that `port selfupdate` does. Which should take care of
 bootstrapping.

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