[MacPorts] #60418: qt4-creator-mac @2.8.1_3 fails building on 10.5.8 PPC

[MacPorts]

#60418: qt4-creator-mac @2.8.1_3 fails building on 10.5.8 PPC
------------------------------+-----------------------
  Reporter:  udbraumann       |      Owner:  michaelld
      Type:  defect           |     Status:  closed
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:  2.6.2
Resolution:  fixed            |   Keywords:  leopard
      Port:  qt4-creator-mac  |
------------------------------+-----------------------

Comment (by kencu):

 So generally speaking a macports installation does not need to use the
 source files from <https://distfiles.macports.org>. The Portfile contains
 the full information to download the source code from the original URL. So
 if the source is missing from distfiles.macport.org, it makes no
 difference.

 But it does to you, because you are on 10.5, and a stock MacPorts
 installation on 10.5 has very old TLS security capability, and most
 current source URLs, being https source URLs so malicious people don't get
 to install crapola software instead of what you thought you were trying to
 install, most of these current source URLs will not work on your 10.5
 macports installation. So you are unable to download any source code
 directly, and have to wait for the Portfile to be committed, and then one
 of Ryan's newer systems that does have current TLS security to download it
 for you form the origin URL, and then mirror it in MacPorts
 distfiles.macports.org, which has downgraded the TLS security so that you
 can use it.

 This works, but having downgraded TLS security is not ideal. But it is
 what it is, and that's why you only get your source code from the
 distfiles mirrors.

 Better all around is to build macports against a current version version
 of software with TLS security -- that's what I do. There is a
 configuration option in Macports to specify the curl version you want to
 build against. It uses the ancient system curl (2005 vintage) when you
 build it, but it uses a current curl (2020 vintage) when I build it.

 The steps to go through are not complicated, but it's an extra few steps,
 and explaining it to people I guess is a bit tedious, so we have not
 required users to do that, so far at least.

 As someone who develops Portfiles, my life would be a misery if I couldn't
 download anything.

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