Please rebuild non-KF packages using ECM's kde_package_app_templates macro with KF 5.79
Friedrich W. H. Kossebau
kossebau at kde.org
Mon Feb 15 22:10:00 GMT 2021
Hi,
the previous ECM 5.78 had a broken version of the macro
kde_package_app_templates(), which generated unusable broken project template
files, which then both KAppTemplate & KDevelop displayed as garbage and could
not use for creating new software projects. The macro itself got fixed for ECM
5.79.
See https://invent.kde.org/frameworks/extra-cmake-modules/-/merge_requests/70
While most usages of that macro are from KF modules (kirigami, kparts,
krunner, ktexteditor, plasma-frameworks), so your latest packages for KF 5.79
would automatically use the fixed ECM 5.79 version, there are also non-KF
projects which also use that macro. So if their latest package was built
against KF/ECM 5.78, those would only provide garbage template files.
So once you have KF 5.79 packages done and published, please also trigger a
rebuild of the following packages against the new version to make sure they
again have working templates (those which are installed to share/
kdevappwizard/templates):
* akonadi
* kdeplasma-addons
* plasma-workspace
(not aware of others, list backed by lxr.kde.org matches)
This note to you is triggered by 2 different persons running into this today
on #kde-devel, so might be worthwhile to care for, given there surely are more
silent ones hitting this.
Cheers
Friedrich
PS: And while at doing package update builds, please also remember to do an
updated package for the recent KDevelop 5.6.2, as that release has a code
switch to catch the behaviour breaking change of some KTextEditor API where
private API (a signal) used by KDevelop changed signature and got public now
in the new KF 5.79, so that needs a rebuild to unbreak.
More information about the Distributions
mailing list