Re: git: 9d76916067d4 - main - Qt5: Update to 5.15.17 (getting down to the end)
- In reply to: Jason E. Hale: "git: 9d76916067d4 - main - Qt5: Update to 5.15.17 (getting down to the end)"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 17 Jul 2025 11:24:06 UTC
On Sun, Jun 15, 2025 at 10:35:45AM +0000, Jason E. Hale wrote: > commit 9d76916067d420d8ea46077ba22e97ce3eaf195c > > Qt5: Update to 5.15.17 (getting down to the end) > > Upstream standard support for Qt5 is officially over. [1] In short, Hi Jason, Doesn't KDE maintain it now and plans to continue indefinitely? > that means get your ports off of Qt5 ASAP, especially end-user > applications. FreeBSD deprecation of Qt5 is coming soon! There are several issues that do not make Qt 6 a drop-in replacement for Qt 5 I'm afraid, both from user's and porter's PoV. In no particular order: USE_QT granularity. Qt 5 is nicely fine-grained, while Qt 6 is more coarse so one has to pull its bits in larger chunks. This is especially annoying because of some hard-coded dependencies. devel/qt6-tools pulls LLVM, so I constantly have to patch it out. I haven't looked into this, but given my dirty hack works it shouldn't be hard to fix this correctly and drop LLVM dependency. Qt 6 unconditionally pulls Wayland (yes, even qt6-base). I keep my systems free of this filth so again have to patch the Makefiles. Could we please make it optional? This is what I can say on top off my head, there are probably others but deprecating Qt 5 and forcing everyone to move to Qt 6 without fixing these would quite probably annoy a large fraction of our users. ./danfe