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.
For all REUSE compatible repositories we can expect that the
license file is stored under LICENSES/ and has the canonical form.
Based on this information, the file checksums can be computed
automatically.
Summary:
While we are renaming it let's also tidy up the bb file.
Reviewers: vkrause
Reviewed By: vkrause
Differential Revision: https://phabricator.kde.org/D24574
Summary:
Overwrite the UDEV_RULES_INSTALL_DIR variable to ensure that the udev rules file is installed in the correct directory.
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Reviewers: vkrause
Reviewed By: vkrause
Differential Revision: https://phabricator.kde.org/D22754
Summary:
Revert "Fix lmdb package QA with latest poky"
This reverts commit 518ddaefbf.
Also do not add binaries to dev packages
Reviewers: #kde_yocto, vkrause
Reviewed By: #kde_yocto, vkrause
Differential Revision: https://phabricator.kde.org/D19660
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:
Extended attributes for the FS are enabled on a distro feature level in Yocto
This check makes Yocto fail in the beginning of a build with an appropriate message
Reviewers: #kde_yocto, vkrause
Reviewed By: #kde_yocto, vkrause
Differential Revision: https://phabricator.kde.org/D19031
