Changes between Version 1 and Version 2 of Ticket #51516, comment 111


Ignore:
Timestamp:
Jun 2, 2024, 12:11:37 PM (6 months ago)
Author:
RJVB (René Bertin)
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #51516, comment 111

    v1 v2  
    99And just to be clear, I'm not suggesting to load `${prefix}/lib/libcurl.?`. It should be loaded from a "hidden" location, installed there in (semi)-permanent fashion and be a variant that does not use OpenSSL (because Pextlib links to the system libcrypto which can clash with the one in MacPorts). It could be installed as a special port (standalone or subport of `port:curl`) which installs only the actual library or installed/updated from a `port-activate` block of one of the suitable variants of `port:curl` itself. A special, dedicated port would make it easier to push updates of course, if and when it's justified to do so given how "base" uses curl.
    1010
    11 Replying to [comment:5 RJVB]:
     11Replying to [https://trac.macports.org/ticket/70127#comment:5 RJVB]:
    1212> Anyway, how much work and how tricky would it be to make `curl.c` load whatever it needs from libcurl dynamically? I'm not against digging into that but if there's already idea of what I'd be getting into I also not against knowing that beforehand :)
    1313