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

MacPorts noreply at macports.org
Sun Jun 2 12:36:11 UTC 2024


#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 ryandesign):

 Replying to [comment:111 RJVB]:
 > the other curl dependents which AFAICT do NOT get revbumped at every
 curl upgrade (except p5-www-curl for a reason I cannot determine).

 WWW::Curl is a perl interface to curl. At the time that p5-www-curl is
 built, it scans the curl.h header and incorporates parts of it into the
 perl module. When the curl port is updated to a new version, p5-www-curl
 is revbumped in case the new curl version's curl.h is sufficiently
 different from the previous one to cause the perl module to change. 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.

 > Given Apple's track record in the matter I don't expect even its latest
 OS has a newer curl version installed than the one in Macports?

 MacPorts usually has the latest version of curl within a few days of its
 release. macOS usually does not.

 > Wading through old mailing lists exchanges is not so much my thing...

 Before embarking on changes to MacPorts, it would be wise to familiarize
 yourself with prior discussion regarding the changes you're planning to
 make. This is to avoid you spending a lot of time making changes if they
 have already been determined to be undesirable for some reason. 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.)

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


More information about the macports-tickets mailing list