On Wed, Jan 7, 2026 at 9:46 PM David Redondo <[email protected]> wrote:
> Happy new year everyone. > > To properly integrate and support Qt5 applications Plasma ships a bunch > of plugins that > still build against Qt5. These are: > > - Qt5 builds of our styles (Breeze and Oxygen) - same code base for Qt5 > and Qt6 > - Qt5 version of the QPT plugin plasma-integration, separate Qt5 code > - kwayland-integration which is needed for KF5 windowsystem, Qt5-only > > Qt5 CI is in the process of being sunset, see: > https://invent.kde.org/sysadmin/repo-metadata/-/work_items/36 > I also get the impression that distros are looking to phase out Qt5, > however I have no feel about how many > Qt5 applications are still out there in the wild. > I would use distributions as my gauge there, the fact distros are moving to eliminate Qt 5 in many places is a good indicator that there aren't many. > > We need to decide what to do with these right now. I see: > - Keep them around but without CI coverage? (my least favourite option for > obvious reasons) > - drop them for Plasma 6.7 and tell distros if they need them build them > from the 6.6 tar ball > - keep them and have some CI setup where we build them against a KF5 stack > from distro packages (if possible) > Keeping a KF5 stack around means a whole different CI VM image to maintain which isn't something i'm terribly thrilled at the idea of. Not sure if you saw the chat, but the VM images and corresponding caches for build resources are not cheap storage wise. > > Did I overlook some other option? > > Cheers, > David > > P.S. with Qt4 we reached this point much later in the cycle. support for > Qt4 variants of breeze and oxygen was > only dropped in 2020 with Plasma 5.18, see: > https://mail.kde.org/pipermail/plasma-devel/2020-January/108585.html > > Thanks, Ben
