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

[MacPorts]

#51516: MacPorts should use a bundled copy of a newer libcurl 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 devans@…):

 Replying to [comment:11 cal@…]:
 > The problem with linking against a copy of OpenSSL in `$prefix` is that
 it will temporarily disappear while OpenSSL itself is upgraded, but that
 must not interrupt the upgrade process.

 Good point.

 >
 >
 > Replying to [comment:10 ryandesign@…]:
 > > Once we are properly mirroring distfiles before doing buildbot builds,
 that will probably be a sufficient fix. But it doesn't help old systems
 download from other sites that require https.
 >
 > No matter what we do, that's a problem these platforms will always have,
 and will continue to do so. As I said, we cannot save abandoned platforms
 from dying.

 Agreed.  However, we can, perhaps, provide tools for those who are
 interested in using these platforms regardless of their antiquity.  I'm
 not sure how many such people there are but they're quite enthusiastic and
 it would be a shame to shun them, altogether, from the MacPorts community.
 Best world, IMO, would be for them to form an ad hoc interest group within
 MacPorts so they could cooperatively work on these issues themselves.

 So I'm suggesting that while we shouldn't commit (and haven't) to
 supporting officially anything older than 10.9, it wouldn't hurt to add a
 hook once in a while to allow them to do the work for themselves if they
 choose to do so. In this case, provide a configuration option for base to
 optionally build with external libraries rather than system ones to solve
 the SSL/TLS issues inherent in the old system libraries.

 By the way, if one wanted to bundle something that is light weight with
 good protocol coverage and permissive licensing, wolfSSL/CyaSSL looks
 interesting.  curl has supported it upstream as an alternative so
 openssl/gnutls for a while now.

-- 
Ticket URL: <https://trac.macports.org/ticket/51516#comment:12>
MacPorts <https://www.macports.org/>
Ports system for the Mac operating system