On Saturday September 03 2016 10:57:24 Ryan Schmidt wrote: >You mustn't change the version in a variant, because MacPorts decides when a >port is outdated based on what's in the portindex, and the portindex only >includes one entry for each port, and the version recorded in the portindex >for a port is the version that would occur with the default variants that were >in effect at the time the portindex was generated
Indeed, that's a sufficient reason to avoid this approach. The argument doesn't entirely fly though for true legacy variants like Qt 5.3.2 which won't ever change version O:^) >Actual data would be required to make a decision. If, for example, 5.7 decided >to drop support for everything older than El Capitan, I would call that >premature and would use that as a reason not to update to 5.7. But then you'd condamn all software that depends on 5.7 features. Either way, if a variant-based approach is out, the issue becomes less urgent (urgent in the sense that I plan to move my qt5-kde-devel port to 5.7 soon, and would have implement the variant logic straight away). When separate ports are required the decision can be made any time to "fork off" the current 5.6 port(s) (or not). R. _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
