From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] classes/rm_work: rename RM_WORK_WHITELIST to RM_WORK_EXCLUDE
Date: Tue, 26 Mar 2013 17:47:26 +0000 [thread overview]
Message-ID: <1364320046-32152-1-git-send-email-paul.eggleton@linux.intel.com> (raw)
This really functions as a blacklist, not a whitelist, since we are
listing recipes to exclude. To avoid any possibility of confusion, since
this was a recent addition, rename the variable.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
---
meta/classes/rm_work.bbclass | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/meta/classes/rm_work.bbclass b/meta/classes/rm_work.bbclass
index 54287bf..1642af7 100644
--- a/meta/classes/rm_work.bbclass
+++ b/meta/classes/rm_work.bbclass
@@ -5,10 +5,10 @@
#
# INHERIT += "rm_work"
#
-# To inhibit rm_work for some recipes, specify them in RM_WORK_WHITELIST.
+# To inhibit rm_work for some recipes, specify them in RM_WORK_EXCLUDE.
# For example, in conf/local.conf:
#
-# RM_WORK_WHITELIST += "icu-native icu busybox"
+# RM_WORK_EXCLUDE += "icu-native icu busybox"
#
# Use the completion scheduler by default when rm_work is active
@@ -19,10 +19,10 @@ RMWORK_ORIG_TASK := "${BB_DEFAULT_TASK}"
BB_DEFAULT_TASK = "rm_work_all"
do_rm_work () {
- # If the recipe name is in the RM_WORK_WHITELIST, skip the recipe.
- for p in ${RM_WORK_WHITELIST}; do
+ # If the recipe name is in the RM_WORK_EXCLUDE, skip the recipe.
+ for p in ${RM_WORK_EXCLUDE}; do
if [ "$p" = "${PN}" ]; then
- bbnote "rm_work: Skipping ${PN} since it is in RM_WORK_WHITELIST"
+ bbnote "rm_work: Skipping ${PN} since it is in RM_WORK_EXCLUDE"
exit 0
fi
done
--
1.7.10.4
reply other threads:[~2013-03-26 18:04 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=1364320046-32152-1-git-send-email-paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--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