[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
Wed Jun 5 12:27:31 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 RJVB):

 Replying to [comment:143 RJVB]:
 > Replying to [comment:141 kencu]:
 > > Your code to use the newer Pextlib looks very promising!
 >
 > I'd *almost* put my hand in the fire that it'll work ;)

 No need. Tried a version of the pkgIndex mod yesterday (on Mac) and it
 works as expected.

 What I didn't expect is that a Pextlib.dylib built from the current HEAD
 of the master branch (so against Tcl 8.6 headers) works with a "base"
 install that's maybe 2 years old now.

 This does beg the question to the powers that be: to what extent would a
 hypothetical `port:MacPorts-pextlib` have to check for/protect against
 installing a new pextlib into an older "base" install?

 I started writing a CMake file for building just Pextlib using
 `-I$prefix/libexec/macports/include` but it quickly became clear that I'd
 have to write an as-yet unknown number of macro definitions in a dedicated
 `config.h` file (or as `-D` arguments).

 If this pextlib port has to be built against the installed Tcl and other
 MacPorts headers I will need to continue working on a dedicated
 buildsystem. If not, the easiest approach will be to run `configure` in
 the toplevel directory of MacPorts source tree, and invoke `make` (and
 `make install`) in the `src/pextlib1.0` source directory. That should
 work.

 Either way it would be helpful if someone who knows the pextlib sources
 really well could dress a list of the various `HAVE_???` defines
 determined by the `configure` script and required by pextlib.

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


More information about the macports-tickets mailing list