qt 6.5.0 removes support for macOS 10.14 and macOS 10.15

[John Hoyt]

Marcus,

I've managed to get the qt6 portfile close to being ready for 6.5.0.  All
of the qt submodules compile locally on intel.  I will be trying on an M1
machine later today.

I could use your advice on how to handle the 6.2 issue.  I'm hesitant to go
too deep down that path before you make any changes to the PG.  Most of
the 6.5 port changes are minor updating submodules, dependencies, and
adding some logic from qt5 to get qtwebengine working.

NOTE: The CI chain is now failing due to timeout.  Is there any way to
extend the timeout?  I know github actions has the capability, but not sure
if it's been wired to a commit message or PR request flag for macports..

Regards,
John

On Wed, Apr 5, 2023 at 7:19 PM John Hoyt <john.hoyt at gmail.com> wrote:

> Marcus,
>
> I'd be very happy to collaborate with you on this!  Also very happy to
> have you become the port maintainer.
>
> It makes a lot of sense to me to update / correct the qt6 portfile and
> PG.  You have a lot more experience that I borrowed from for the
> initial qt6 portfile and PG.  Happy to have your improvements here.
>
> Thanks!
> John
>
> On Wed, Apr 5, 2023 at 9:04 AM <mcalhoun at macports.org> wrote:
>
>> I have not looked at the specific issues with Qt 6.5.
>> However, based on our experience with the Qt5 ports, I would suggest
>> sticking to the upstream recommendations concerning supported versions.
>>
>> For Qt5, most of the incompatibilities were in parts of the OS that
>> LegacySupport and other mechanisms could not get around.
>> Even if the current version works on older systems now, changes in the
>> patch version have introduced incompatibilities.
>>
>> -Marcus
>>
>> > On Apr 5, 2023, at 5:31 AM, Chris Jones <jonesc at hep.phy.cam.ac.uk>
>> wrote:
>> >
>> > Hi,
>> >
>> > Just to add, it would also be useful to know a bit on the reasons for
>> dropping the older OSes, what exactly are the tehcnical reasons for it, as
>> within macports we have a number of build options available to us, like
>> newer builds of the compilers which can be used instead of the Xcode
>> versions, that help us support a lot of ports on systems way older than
>> upstream for them officially support.
>> >
>> > cheers Chris
>> >
>> > On 05/04/2023 2:02 am, John Hoyt wrote:
>> >> Renee,
>> >> Thanks for the pointers - I'll take a look with fresh eyes tomorrow.
>> I've added a todo list in the PR, as it's very much a WIP - although I have
>> been able to successfully build all subports locally (still have to test
>> and attempt to build on arm).
>> >> Just a heads up - Qt6.5 seems to be a little different than the work
>> we've done on Qt 6.2.  Some of the qt5 based CMake updates seem to no
>> longer be necessary (and in some cases now break things forcing incorrect
>> paths).
>> >> Regards,
>> >> John
>> >> On Tue, Apr 4, 2023 at 8:39 PM Renee Otten <ottenr.work at gmail.com
>> <mailto:ottenr.work at gmail.com>> wrote:
>> >>    hi John,
>> >>    Thanks for working on that! Regarding the support of older macOS
>> >>    versions: The Qt5 PortGroup and ports are the example on how this
>> >>    was done for Qt5 and likely on how to do the same for Qt6.
>> >>    I likely will not have time to do much work on this myself but will
>> >>    look at the PR and see if I can provide some help…
>> >>    Best,
>> >>    Renee
>> >>>    On Apr 4, 2023, at 8:32 PM, John Hoyt <john.hoyt at gmail.com
>> >>>    <mailto:john.hoyt at gmail.com>> wrote:
>> >>>
>> >>>    
>> >>>    I've started working on updating the qt6 port to qt 6.5.0 (see
>> >>>    https://github.com/macports/macports-ports/pull/18186
>> >>>    <https://github.com/macports/macports-ports/pull/18186>).
>> >>>
>> >>>    Qt 6.5.0 removed support for macOS 10.14 and 10.15, only
>> >>>    supporting macOS 11 and newer whereas qt 6.2 supports macOS >=
>> 10.14.
>> >>>
>> >>>    Any suggestions on how to handle the deprecation of macOS 10.14
>> >>>    and 10.15?
>> >>>
>> >>>    Thanks,
>> >>>    John
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20230408/5fd1ab2d/attachment.htm>