I believe this is possible.
However, as Ken pointed out in a previous email, we have two models we could
follow:
1) The gtk3 +quarts vs gtk3 +x11 model
(Almost) every dependent port of gtk3 has quartz and x11 variants
consistent with whatever gtk3 was installed with.
I *think* this could be done in the qt5 PortGroup.
Every port which uses PortGroup qt5 would get a qt5LTS variant (or a better
name).
We already have some the machinery for the long delayed qt5kde variant.
2) The multiple LLVM/GCC versions model
Most of Qt 5 is installed into ${prefix}/libexec/qt5.
The exceptions are the cmake and pkgconfig files.
We could try to allow multiple simultaneous installations of Qt.
Each port would then be free to choose whichever is better.
I am not sure which (if either) would be a good design choice.
-Marcus
> On May 11, 2018, at 3:55 AM, Craig Treleaven <[email protected]> wrote:
>
> Would there be some way to designate that a port wishes to rely only on LTS
> versions? AIUI, Qt 5.6 and 5.9 are currently the long term support versions.
> Qt 5.6 is supported on macOS 10.8, 10.9, 10.10, 10.11. (“Deployment only on
> 10.7”, they say.) Qt 5.9 is supported on macOS 10.10, 10.11, 10.12.
> Presumably it also works on 10.13. Qt 5.5 is defacto supported on earlier
> platforms.
>
> qt5.get_default_name would effectively become:
>
> os.major 9 through 11, qt55
> os.major 12 through 14, qt56
> os.major after13, qt59
>
> When the Qt project releases a new LTS version, I would recommend that we NOT
> recognize it as LTS for our purposes until at least the first major bug fix
> release.
>
> I hope I haven’t missed something blindingly obvious.
>
> Craig
>
