From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: [PATCH] sstate.bbclass: Remove hardcoded task mappings
Date: Thu, 30 Aug 2012 17:27:11 -0700 [thread overview]
Message-ID: <1346372831.16485.15.camel@ted> (raw)
I've not idea why this got left in but as per the comment, it needs fixing
and we shouldn't have hardcoded mappings like this. Lets remove it
and dynamically generate the data instead.
[YOCTO #3039]
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass
index 6762e32..e4b70b3 100644
--- a/meta/classes/sstate.bbclass
+++ b/meta/classes/sstate.bbclass
@@ -519,16 +519,9 @@ BB_HASHCHECK_FUNCTION = "sstate_checkhashes"
def sstate_checkhashes(sq_fn, sq_task, sq_hash, sq_hashfn, d):
ret = []
- # This needs to go away, FIXME
- mapping = {
- "do_populate_sysroot" : "populate-sysroot",
- "do_populate_lic" : "populate-lic",
- "do_package_write_ipk" : "deploy-ipk",
- "do_package_write_deb" : "deploy-deb",
- "do_package_write_rpm" : "deploy-rpm",
- "do_package" : "package",
- "do_deploy" : "deploy",
- }
+ mapping = {}
+ for t in d.getVar("SSTATETASKS", True).split():
+ mapping[t] = d.getVarFlag(t, "sstate-name", True)
for task in range(len(sq_fn)):
spec = sq_hashfn[task].split(" ")[1]
reply other threads:[~2012-08-31 8:03 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=1346372831.16485.15.camel@ted \
--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