@Zren: Updated! Thanks for pointing this out!

Thanks, I'll keep that in mind for next time.

Thanks for the feedback, I've looked some more into what the KPackage does and I agree that it doesn't make sense to disable it in general. Closing this.

But what if my application runs sandboxed in the desktop and does its file selection through portals? I'd still want it to have maximum desktop integration under KDE if possible. Hence I want to include plasma-integration as well, or is my thinking wrong here?

Since these changes have been approved and marked read-to-land for quite some time, could this please be done soon? Thank you!

Updated to latest KF5 version and probably fixed the issue mentioned in review – although I have no idea what it was.

The target application I'm building has only very minimal dependencies on Qt (just QtCore + QtWidgets + PyQt5) and no real dependencies on KDE. The application only has a size footprint of about 6MiB, the required Qt libraries use about 10MiB of space, the selected set of KDE integration libraries (a minimalist build of the KDE plasmaintegration package including dependencies) add another 10MiB. By contrast org.kde.Platform alone adds more than 150MiB in size requirements – this is not acceptable for an app that uses less than 20% percent of its contents IMHO. You can take a look at the project here. I'm planning on making this available as a runtime extension for the FreeDesktop runtime so that other people can reuse it too.

@ngraham: I've updated the patch to the latest GIT master of breeze. A quick test compile without qtdeclarative5-dev suggests that it still works.

That would be „Alexander Schlarb <alexander@ninetailed.ninja>“. Thanks!

I build a Qt app with „just enough“ KDE-integration for the Flatpak sandbox where I have no use for this KPackage stuff. I know I could just include the install handlers in the build and drop them afterwards, but that would require a build KNS (and all of *its* dependencies) as well. IMHO „only build what you use“ is surpreme in this case.

Oh, I see! This wasn't obvious to me. Is this better now?

Thanks for accepting this! Please also add it to the code repository!

Any review of this would be greatly apprechiated…

Could I get a new review on this please!?

I used the web interface and I wasn't able to find the „Update Diff“ button (why not update patch or update commit?) in the right box until now. It should be fixed now.