Re: [OE-core][PATCH] kernel-dummy: fix executing unexpected tasks


 

On Wed, 25 Nov 2020 at 16:56, Andrej Valek <andrej.valek@siemens.com> wrote:

- refactor kernel dummy recipe
- remove unneeded COPYING.GPL file -> change license to close
- remove unneeded tasks (fetch, unpack, pack)
- do not run unneeded tasks, but keep deps (configure, compile, install)
- save files into sstate
- fix: ERROR: Task linux-dummy.do_fetch attempted to execute unexpectedly

Signed-off-by: Andrej Valek <andrej.valek@siemens.com>
---
meta/recipes-kernel/linux/linux-dummy.bb | 28 +-
meta/recipes-kernel/linux/linux-dummy/COPYING.GPL | 339 ----------------------
2 files changed, 12 insertions(+), 355 deletions(-)
delete mode 100644 meta/recipes-kernel/linux/linux-dummy/COPYING.GPL

diff --git a/meta/recipes-kernel/linux/linux-dummy.bb b/meta/recipes-kernel/linux/linux-dummy.bb
index 62cf6f5ea6..e98a29d5c6 100644
--- a/meta/recipes-kernel/linux/linux-dummy.bb
+++ b/meta/recipes-kernel/linux/linux-dummy.bb
@@ -4,11 +4,12 @@ provider for virtual/kernel to satisfy dependencies for situations \
where you wish to build the kernel externally from the build system."
SECTION = "kernel"

-LICENSE = "GPLv2"
-LIC_FILES_CHKSUM = "file://${WORKDIR}/COPYING.GPL;md5=751419260aa954499f7abaabaa882bbe"
+LICENSE = "CLOSED"
I don't think "CLOSED" is a good choice to use in the core metadata.
The usual way to handle recipes like this which don't require external
source code is to say that they have the same license as the core
metadata itself (MIT) and reference the license text in
"meta/COPYING.MIT". See for example
meta/recipes-bsp/formfactor/formfactor_0.0.bb.

Thanks,

--
Paul Barker
Konsulko Group

Join yocto@lists.yoctoproject.org to automatically receive all group messages.