Qt6/KF6 migration plan
While building against Qt6/KF6 isn't much of an issues there's some consideration needed for deploying.
KAccounts consists of several pieces:
- A library that applications use. This is used by e.g. purpose, kio-gdrive, and Akonadi. This means we need a Qt5 and Qt6 version of the library simultaneously.
- A qml module, used by the KCM.
- A kded module. This module does two things: 1) The org.kde.Accounts DBus interface, which looks unused. 2) Load kaccounts daemon plugins. As far as I can tell two such plugins exist: One from kio-gdrive to pop up a notification when a new Google account is added and one from kaccounts-integration to add shortcuts for webdav entries to Dolphin
- A KCM. This is used from both systemsettings and opened by applications
Providing a Qt5 and Qt6 variant of the library isn't really avoidable but easy enough to do. For the rest it gets a bit tricky.
The answers here somewhat depend on the question whether it's safe to assume that the Gear 24.02 release will only be used with Plasma 6 (instead of Plasma 5; running outside of Plasma must of course also stay possible to the degree it is now).