[MacPorts] #62441: qBittorrent fails to build on OS X 10.10.5

[MacPorts]

#62441: qBittorrent fails to build on OS X 10.10.5
-----------------------------------+------------------------
  Reporter:  DanielSmedegaardBuus  |      Owner:  i0ntempest
      Type:  defect                |     Status:  assigned
  Priority:  Low                   |  Milestone:
 Component:  ports                 |    Version:  2.6.4
Resolution:                        |   Keywords:  yosemite
      Port:  qbittorrent           |
-----------------------------------+------------------------

Comment (by DanielSmedegaardBuus):

 Yes, I too use pinning with apt (and previously with brew). It's nice to
 have :) But of course, it makes a lot of sense to have that option also on
 the maintainer-side with something like Macports, where you maintain so
 many previous versions of macOS.

 The reference to mkvtoolnix earlier got me remembering that I needed that
 installed too, and I noticed that the latest version offered to my system
 is v41, which I myself had noted was the last one I could download from
 fosshub and run on Yosemite. For old grumpy farts like me who think that
 macOS has, in key areas, gotten worse with every installment since
 Mavericks (not to say that it hasn't improved in others), hunting for
 compatible versions is an annoyance, but also a bit of a curiosity, as it
 doesn't always make sense.

 For instance, I get that the dependency on Qt in mkvtoolnix-gui can cause
 mkvtoolnix itself to lose support when it is built against newer versions
 of Qt that have their own new dependencies. But then something like
 qBittorrent 4.3.2 actually being available for Yosemite here, in Macports,
 indicates that this is most likely just laziness or sloppiness on the
 behalf of the developers. Also, in the case of mkvtoolnix, a) The GUI has
 looked exactly the same for as long as I remember, so why not stick with
 the more compatible version of Qt?, and b) Why are the CLI also
 incompatible with older versions? There's no reason I can think of that
 these tools shouldn't be compatible with pretty much any system out there,
 just link statically. Or maybe that's just bad practice. But I do enjoy my
 decades-old CLI binaries that were built with static linking, that still
 work everywhere, all the time.

 Well, sorry, I know this isn't a chat room, I should use my inside-voice
 for my rants :D I'm very curious about your link, Ken. It's been about 15
 years since I last did any C/++ programming, so I'm rusty with compiling
 and linking and whatnot, but in general terms I get what you're trying to
 do over there, and I really like it. It reminds me of compiling on
 Windows, where — if I'm not misremembering — libraries are loaded a bit
 like the shell uses its $PATH, so that you can override linked libraries
 with custom versions by placing them further up in the path, e.g. right
 next to the executable. But that's been about 20 years, so I may remember
 incorrectly, or the may have changed it since :D Either way, I applaud any
 work that's done to keep the golden years (in my view) of OS X alive for
 as long as possible ;)

 i0ntempest, If you're going to do the server-side pinning of qbt version
 4.3.2 for Yosemite, I'd love to know, so I can remove the mental note to
 avoid upgrading :D

 Thank you guys!

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