Handing QML dependencies

[Hefee]

Hey,

> Interesting. So far we have avoided doing that as much as possible
> because there is no way QML files are needed upon build time, thus
> reducing build space, there was no benefit. Now there is a tangible
> benefit for this. This could also mean we can keep the CMake files
> that look for specific QML plugins to be available upon build time...
> but this might make some apps FTBFS, which might be fixed with a
> proper unstable rebuild (ask Lucas IIRC) + transition.

at least KF6 already have checks to check for qml dependencies and also 
requiring them, but KF6 also ships the needed cmake stuff to detect the qml 
depends.
e.g. itinerary/CMakeLists.txt:
ecm_find_qmlmodule(org.kde.kosmindoormap 24.02 REQUIRED)

> I would personally say "Go for it, and if someone complains then let
> them provide a workaround".

thanks for that;)

Regards,

hefee
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-kde-talk/attachments/20241012/148a5d4c/attachment.sig>