The change was performed as follows:
- it was checked that the COPYING.MIT license was present with the
initial commit and such each contributor was awere of the license
- mail was around to all previous contributors to check this assumption
(mail was not replied by Hannah and Sebastian); every reply was a
confirmation of the assumed MIT licensing
- all copyright information were recovered from the respective Git
commits
- reuse lint was to used to check the REUSE conformance
After recent conversion of KF5 repositories to SPDX, the outbound
licenses are much more clear. As a first step, introduce the lowest
available license version into the package. Note that many packages
are dual-licenses (e.g. LGPL-2.0-only or LGPL-2.1-only), which is
not yet respected in the statements.
The previous hack of just copying the native tools into the target sysroot
has several limitations:
- it no longer works with relative RPATHs being used
- it fails in the case of kpackage where we need the same tools for host
and target
Summary: Drop a number of upstreamed patches, move Kirigami from staging to tier 1.
Reviewers: cordlandwehr
Reviewed By: cordlandwehr
Differential Revision: https://phabricator.kde.org/D7396
Summary:
We now no longer need the corresponding native variants of the frameworks
added as explicit dependencies, the target ones take care of this. The
approach is inspired by how the Wayland recipe handles its code generator.
This also uncovered an issue with KAuth, which can't build its host tools
yet. This uses the target version as a placeholder for now, to not block
the build of everything else.
Reviewers: cordlandwehr
Reviewed By: cordlandwehr
Differential Revision: https://phabricator.kde.org/D7023
Summary:
Also, move it to tier3 where it belongs. Required fixes in KConfig too,
to actually make it usable as a dependency.
Reviewers: cordlandwehr
Reviewed By: cordlandwehr
Differential Revision: https://phabricator.kde.org/D6996
Summary:
Based on Johan's work branch. This also disables unit tests for all
frameworks, tests aren't executable for cross-builds anyway, and KConfig
tries to run the target kconfig_compiler there.
The native version can still further improved by allowing a QtCore-only
build of KConfig, as we are only interested in the kconfig_compiler.
Reviewers: cordlandwehr
Reviewed By: cordlandwehr
Differential Revision: https://phabricator.kde.org/D6987
