Summary:
use the new package install macro to install them as
as rcc files
Test Plan:
plasmashell starts and most plasmoids seem to work,
still needed a more thorough test
Reviewers: #plasma
Subscribers: davidedmundson, apol, plasma-devel, #frameworks
Tags: #plasma, #frameworks
Differential Revision: https://phabricator.kde.org/D9400
Summary:
Using a private flag just added for plasma_install_package, until
there is a new official replacement for kpackage_install_package for
its needs
Test Plan: kdeplasma-addons & Co still build and now have clean cmake log again.
Reviewers: mart, apol
Reviewed By: mart
Subscribers: #frameworks
Tags: #frameworks, #plasma
Differential Revision: https://phabricator.kde.org/D11130
Summary:
Currently plasma_install_package fails if KDE_INSTALL_DIRS_NO_DEPRECATED
is set to TRUE, because the macro is still using the deprecated vars
DATA_INSTALL_DIR & SERVICES_INSTALL_DIR.
It should be fine to bump the min version of ECM required to needed ECM 1.6.0,
as someone using KF5 5.26 very surely also has a similar recent ECM.
Reviewers: #plasma, sebas, mart
Reviewed By: mart
Subscribers: plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D2633
Plasma packages are essentially kpackages, so use the macros from KPackage
to install Plasma packages.
This allows to reuse the facilities set up there.
REVIEW: 128579
In the SDDM theme (and a few other places) I leave some notes for other
developers; I need to add one to the workspace components too.
As plasma_package blindly copies everything it seems to annoy packagers.
Change-Id: I77765f96f1a5fb24a7788f69eae1bbffaf14210b
At the moment, we could say that plasma is co-installable by chance,
it's only working because KF5 dropped the apps relative directory.
This change introduces a PLASMA_RELATIVE_DATA_INSTALL_DIR that will
be available to know where in share the components are and
PLASMA_DATA_INSTALL_DIR to know where data has to be installed to.
Reviewed by David Edmundson
CCMAIL: plasma-devel@kde.org
