https://bugs.kde.org/show_bug.cgi?id=369232
--- Comment #2 from Harald Sitter <sit...@kde.org> --- I have to confess I am going a bit TLDR on the response but I think the key problem is that previously before cmake RUNTIME we didn't have a way to communicate runtime deps in a *standardized* way. Which means packagers had no chance to deal with them efficiently. They now do, exactly the way as we do with other dependencies. If they don't make use of that, then they are just being bad at their job. find_package could even be made required and skipped with CMAKE_DISABLE_FIND_PACKAGE_$NAME by the packagers. So you get the same end result but you do it in a standard fashion. Regardless of any of this. I cannot think of a single packaging environment where build environment == run environment. The rcc being there at buildtime doesn't mean anything WRT runtime. On deb/rpm the rcc would need to be a runtime dep. In snap/flatpak/appimage the rcc needs to end up in the bundle (which fortunately is the default), same on other platforms. You need to assert it as runtime dependency in a standard fashion, everything else is just wishful thinking. -- You are receiving this mail because: You are watching all bug changes.
