<div dir="ltr">Marcus,<div><br></div><div>Just a minor update. I think I have the qt 6.5. PR ready for a review. I just pushed the logic that selects qt6.2 for the now unsupported versions of macOS ( < 11).</div><div><br></div><div>I am struggling with qtwebengine some and may remove it and qtwebview (qtwebengine is.a dependency) Just to get this moving forward.</div><div><br></div><div>Happy to have others review and make suggestions on qtwebengine as well.</div><div><br></div><div>Thanks!</div><div>John</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Apr 8, 2023 at 7:56 AM John Hoyt <<a href="mailto:john.hoyt@gmail.com">john.hoyt@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Marcus,<div><br></div><div>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.</div><div><br></div><div><div>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.</div></div><div><br></div><div>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..</div><div><br></div><div>Regards,</div><div>John</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 5, 2023 at 7:19 PM John Hoyt <<a href="mailto:john.hoyt@gmail.com" target="_blank">john.hoyt@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Marcus,<div><br></div><div>I'd be very happy to collaborate with you on this! Also very happy to have you become the port maintainer.</div><div><br></div><div>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.</div><div><br></div><div>Thanks!</div><div>John</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 5, 2023 at 9:04 AM <<a href="mailto:mcalhoun@macports.org" target="_blank">mcalhoun@macports.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I have not looked at the specific issues with Qt 6.5.<br>
However, based on our experience with the Qt5 ports, I would suggest sticking to the upstream recommendations concerning supported versions.<br>
<br>
For Qt5, most of the incompatibilities were in parts of the OS that LegacySupport and other mechanisms could not get around.<br>
Even if the current version works on older systems now, changes in the patch version have introduced incompatibilities.<br>
<br>
-Marcus<br>
<br>
> On Apr 5, 2023, at 5:31 AM, Chris Jones <<a href="mailto:jonesc@hep.phy.cam.ac.uk" target="_blank">jonesc@hep.phy.cam.ac.uk</a>> wrote:<br>
> <br>
> Hi,<br>
> <br>
> 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.<br>
> <br>
> cheers Chris<br>
> <br>
> On 05/04/2023 2:02 am, John Hoyt wrote:<br>
>> Renee,<br>
>> 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).<br>
>> 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).<br>
>> Regards,<br>
>> John<br>
>> On Tue, Apr 4, 2023 at 8:39 PM Renee Otten <<a href="mailto:ottenr.work@gmail.com" target="_blank">ottenr.work@gmail.com</a> <mailto:<a href="mailto:ottenr.work@gmail.com" target="_blank">ottenr.work@gmail.com</a>>> wrote:<br>
>> hi John,<br>
>> Thanks for working on that! Regarding the support of older macOS<br>
>> versions: The Qt5 PortGroup and ports are the example on how this<br>
>> was done for Qt5 and likely on how to do the same for Qt6.<br>
>> I likely will not have time to do much work on this myself but will<br>
>> look at the PR and see if I can provide some help…<br>
>> Best,<br>
>> Renee<br>
>>> On Apr 4, 2023, at 8:32 PM, John Hoyt <<a href="mailto:john.hoyt@gmail.com" target="_blank">john.hoyt@gmail.com</a><br>
>>> <mailto:<a href="mailto:john.hoyt@gmail.com" target="_blank">john.hoyt@gmail.com</a>>> wrote:<br>
>>> <br>
>>> <br>
>>> I've started working on updating the qt6 port to qt 6.5.0 (see<br>
>>> <a href="https://github.com/macports/macports-ports/pull/18186" rel="noreferrer" target="_blank">https://github.com/macports/macports-ports/pull/18186</a><br>
>>> <<a href="https://github.com/macports/macports-ports/pull/18186" rel="noreferrer" target="_blank">https://github.com/macports/macports-ports/pull/18186</a>>).<br>
>>> <br>
>>> Qt 6.5.0 removed support for macOS 10.14 and 10.15, only<br>
>>> supporting macOS 11 and newer whereas qt 6.2 supports macOS >= 10.14.<br>
>>> <br>
>>> Any suggestions on how to handle the deprecation of macOS 10.14<br>
>>> and 10.15?<br>
>>> <br>
>>> Thanks,<br>
>>> John<br>
<br>
</blockquote></div>
</blockquote></div>
</blockquote></div>