From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: [PATCH] license: Fix BB_TASKDEPDATA references
Date: Tue, 15 Dec 2015 16:40:36 +0000 [thread overview]
Message-ID: <1450197636.13505.74.camel@linuxfoundation.org> (raw)
We shouldn't try and expand what is a python dict object
and we don't want it to influence the task hashes, task
dependencies are already accounted for.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
diff --git a/meta/classes/license.bbclass b/meta/classes/license.bbclass
index be1e0e7..6651d55 100644
--- a/meta/classes/license.bbclass
+++ b/meta/classes/license.bbclass
@@ -192,7 +192,7 @@ def get_deployed_dependencies(d):
# usually in this var and not listed in rootfs.
# At last, get the dependencies from boot classes because
# it might contain the bootloader.
- taskdata = d.getVar("BB_TASKDEPDATA", True)
+ taskdata = d.getVar("BB_TASKDEPDATA", False)
depends = list(set([dep[0] for dep
in taskdata.itervalues()
if not dep[0].endswith("-native")]))
@@ -228,6 +228,7 @@ def get_deployed_dependencies(d):
break
return deploy
+get_deployed_dependencies[vardepsexclude] = "BB_TASKDEPDATA"
def get_boot_dependencies(d):
"""
@@ -236,7 +237,7 @@ def get_boot_dependencies(d):
depends = []
boot_depends_string = ""
- taskdepdata = d.getVar("BB_TASKDEPDATA", True)
+ taskdepdata = d.getVar("BB_TASKDEPDATA", False)
# Only bootimg and bootdirectdisk include the depends flag
boot_tasks = ["do_bootimg", "do_bootdirectdisk",]
@@ -264,6 +265,7 @@ def get_boot_dependencies(d):
depends.append(taskdep[0])
break
return depends
+get_boot_dependencies[vardepsexclude] = "BB_TASKDEPDATA"
def get_deployed_files(man_file):
"""
reply other threads:[~2015-12-15 16:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1450197636.13505.74.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox