Josh, could you tell me more about your preferred method of handling ports that need to be available in different versions on different systems?
In https://trac.macports.org/ticket/74078#comment:55 you said: > I don't want to start a debate again, but just to be clear, my > preferred solution is to have separate ports (or subports) providing > the different versions of the software, with a stub port that depends > on the correct versioned port according to the OS version. I'm not trying to debate; I just don't think I understand your method well enough to implement it. Maybe you could talk me through it with an example like libheif. Before this month's update, we had a libheif port offering 1.18.2 to macOS 10.6 and earlier and 1.21.2 to macOS 10.7 and later. Under your method, would this have been two or three separate ports, what would they have been called, and what files would each install? Are they all simultaneously installable or do some of them conflict with one another? Then on June 1 the port was updated to 1.23.0. Based on the assumption that this would work on all systems that 1.21.2 worked on, how would this update have been handled using your method? As it turns out, 1.23.0 has problems building on macOS 10.15 and later, so we now have a port that offers 1.18.2 to macOS 10.6 and earlier, 1.22.2 to macOS 10.7 thru 10.14, and 1.23.0 to macOS 10.15 and later. How would this change be done with your method? Or are there existing ports that embody your method that I could look at?
