Port the actions to use the KCoreAddons plugin infrastructure instead of using KService. Using it for such purposes will be deprecated
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T12171 Meta task: KService | ||
| Open | None | T12173 KService: provide solution to migrate away from KServiceTypeTrader/KMimeTypeTrader for loading plugins and parts | ||
| Open | alex | T12248 Port PowerDevil actions to plugins |
Comment Actions
Question is if we need a plug in infrastructure in the first place.
I am not aware of any 3rd party plug-ins. Even the network manager qt stuff is in PowerDevil ...
Comment Actions
https://invent.kde.org/plasma/powerdevil/-/merge_requests/48 bundles the only non-builtin action. After that we can probably get rid of the plugin stuff
Comment Actions
I am wondering to what extend this is considered public API. For example the dolphin VSC plugins are also only internally used, but when they were ported to KPluginLoader the old style plugin loading was kept.