Qt5 build removal

Development
1

Hi,

I know qt6 has been around enough time, but still some have systems based on qt5, and hence removing qt5 will cause us to get stuck on the last release and not being able to add anything new.

Would it be a problem to keep qt5 still?

I get it probably requires extra maintenance work, but I have to ask …

Thanks in advance.

2

Qt5 and Qt6 are co-installable, you don’t need to choose. Just use whatever the app needs.

Then it is a distribution choice when to remove qt5 packages. It mostly depends on which and how many “major” applications haven’t switched (obs, krita…).

3

Well, I meant to say qt5 removal from Skrooge build.

4

As far the KDE CI infrastructure is concerned you don’t have a choice though, Qt5 is going away there shortly: Dropping Qt5 CI Support at the End of September 2025. That is extremely unlikely to change as it gets increasingly hard to keep that running while increasingly fewer repos need it.

5

I guess for some porters around here the main (or one of) issue is with libQt5Webengine, which are not available for Qt6 versions (yet).
At least it’s one major issue on moving some KDE ports over to Qt6. (not that many but still).

6

It would be a problem. Commit Remove Qt5 build has SET(KF_MIN_VERSION "6.3.0"). You’d have to maintain a fork or contract with someone to do so.

If you’re using the flatpak, the update to KDE Frameworks 6/Qt6 probably won’t affect your systems. The current Skrooge v25.4.0 flatpak on Flathub is still based on KDE 5.15, but the “nightly” flatpak build from KDE CI has switched and I assume Flathub will when 25.5 is released.

Thanks Stéphane (@miraks) for the port to 6, it must have been a lot of work.