From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 1/2] base.bbclass: clarify COMMERCIAL_LICENSE skip reason
Date: Tue, 23 Aug 2011 23:32:45 +0100 [thread overview]
Message-ID: <67afbdbdca8b47638e5710d9de2961b1cae469e1.1314138692.git.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <cover.1314138692.git.paul.eggleton@linux.intel.com>
In-Reply-To: <cover.1314138692.git.paul.eggleton@linux.intel.com>
Change to a proper sentence and add a reference to the
COMMERCIAL_LICENSE variable so that the user knows where this can be
controlled.
Addresses remainder of [YOCTO #846]
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
---
meta/classes/base.bbclass | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
index 4332d24..3501f4b 100644
--- a/meta/classes/base.bbclass
+++ b/meta/classes/base.bbclass
@@ -345,7 +345,7 @@ python () {
pnr = pn.replace('+', "\+")
if commercial_license and re.search(pnr, commercial_license):
bb.debug(1, "Skipping %s because it's commercially licensed" % pn)
- raise bb.parse.SkipPackage("because it requires commercial license to ship product")
+ raise bb.parse.SkipPackage("because it may require a commercial license to ship in a product (listed in COMMERCIAL_LICENSE)")
# If we're building a target package we need to use fakeroot (pseudo)
# in order to capture permissions, owners, groups and special files
--
1.7.4.1
next prev parent reply other threads:[~2011-08-23 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 22:32 [PATCH 0/2] Couple of fixes Paul Eggleton
2011-08-23 22:32 ` Paul Eggleton [this message]
2011-08-23 22:32 ` [PATCH 2/2] scripts/combo-layer: fix overzealous regex in default hook script Paul Eggleton
2011-08-24 12:36 ` Otavio Salvador
2011-08-24 1:33 ` [PATCH 0/2] Couple of fixes Richard Purdie
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=67afbdbdca8b47638e5710d9de2961b1cae469e1.1314138692.git.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