On 2022-7-21 03:32 , Dave Allured - NOAA Affiliate via macports-dev wrote:
On Wed, Jul 20, 2022 at 2:30 AM Christopher Jones <jon...@hep.phy.cam.ac.uk <mailto:jon...@hep.phy.cam.ac.uk>> wrote:On 20 Jul 2022, at 1:13 am, Dave Allured - NOAA Affiliate via macports-dev <macports-dev@lists.macports.org <mailto:macports-dev@lists.macports.org>> wrote: Hmmm. If port curl is already installed and active, then why would subsequent port fetches prefer /usr/bin/curl? Is this a search path issue?No. port does not rely on finding ‘curl’, from PATH. It instead uses the system lib curl which it is liked against. The only way to get port to use a different curl is to rebuild base, configured to use that version.Ah, that is what I missed. How about adding a fallback option to use an alternate command line curl through PATH, when available, after normal fetch attempts have failed? My hope is that this would ultimately reduce time spent on debugging connection and SSL issues.
One of the several reasons why we mirror distfiles is that it makes issues like this non-issues for users most of the time. If downloading from a particular server fails, MacPorts just moves on to trying the next mirror.
- Josh
