https://bugs.kde.org/show_bug.cgi?id=400999
Bug ID: 400999
Summary: kpackage implicitly pulled in and never reported on
Product: kirigami gallery
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: notm...@gmail.com
Reporter: sit...@kde.org
Target Milestone: ---
The cmakelists contains the following:
> find_program(kpackagetool_cmd kpackagetool5)
The result of this is not ever recorded in the summary. This makes it entirely
in-obvious to distributions why appdata is not present for the tool (seeing as
cmake never complains that kpackagetool is missing)
It's also always 100% less accurate than what the actual kpackage cmake targets
would do, as those will always import the correct path it was installed to, not
any old binary it may find in $PATH (which may be rubbish or broken).
As a solution I suggest to write the appdata manually and throw kpackagetool
out the window. Notably kpackagetool won't know that this is in application,
and as application its appdata should have a launchable key. Also see bug
400998 which mentions that no appdata file is also an approach; albeit
resulting in less quality appdata.
--
You are receiving this mail because:
You are watching all bug changes.
