#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@…): I agree that bundling an SSL library could lead to a lot of extra cycles to update the bundle for security issues, etc. Also probably licensing issues with a binary bundle that includes OpenSSL or LibreSSL. Not sure about other SSL libraries. To avoid these issues, could we set it up so a source build could be built with an external library other than the system ones? An interested user could then boot strap from an outdated binary Installer like this: * install old port binary using installer * build the SSL library of your choice using the just installed port binary * do a source build using the installed non-system SSL library using the appropriate configuration parameters ( say `--with-openssl=${prefix}/lib` ) This avoids binary licensing issues and updates for OpenSSL and the like would be handled by the normal port maintenance process. The procedure would need to be well documented to avoid too many "I tried it but it didn't work" tickets. Or is this too complicated for the average user to deal with? Just an idea. -- Ticket URL: <https://trac.macports.org/ticket/51516#comment:8> MacPorts <https://www.macports.org/> Ports system for the Mac operating system