https://bugs.kde.org/show_bug.cgi?id=446731
--- Comment #5 from Wolfgang Bauer <wba...@tmo.at> --- (In reply to Jarosław Staniek from comment #4) > Thanks for the bigger picture Wolfgang. IIRC back when we lacked the > build-time check we had situations when KEXI was distributed without the > dependency. Would you see a universal replacement technique to ensure > declared run time dependencies are met? (other than mention in > README.PACKAGERS that depends on human nature) Not really, no. Except that it would be possible to specify the runtime dependency in the cmake files, but that might get overlooked too... > First thing we added was the runtime check. Before that missing icons was > confusing to the user. Not it is confusing too, but at least we can warn in > a message that the KEXI software isn't 100% properly distributed. Well, it is not a warning, but an error. Currently, Kexi just quits if the .rcc is not installed, even if the icons are available because the breeze icon theme is installed. > > Maybe just use the standard icons if the .rcc is not available on build > > time? > > That is the central issue. Standard icons do not include icons that KEXI > requires. So the software looks random and unfinished. > That's the cost of centralization (having a central icon project in KDE > while we can't control "central" desktop environment). Ok, you probably have a point there. That was just a thought. So maybe add a cmake option to build without the .rcc dependency, disabled by default? (or the opposite, have a cmake option to build with the .rcc dependency that is enabled by default) Maybe @Fabian could make a suggestion as well here though. -- You are receiving this mail because: You are watching all bug changes.