From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/1] Add recipe whitelisting class
Date: Thu, 27 Aug 2015 13:36:52 +0100 [thread overview]
Message-ID: <cover.1440678731.git.paul.eggleton@linux.intel.com> (raw)
Changes since the RFC version:
* Check BPN in addition to PN for matching, to make it easier in the
multilib case
* Use PNWHITELIST_LAYERS to specify which layers to apply whitelisting to,
and consider an empty whitelist value to be no recipes whitelisted (so
you can set up empty whitelists for layers not yet in your
configuration if you wish to do so). This also makes setting
PNWHITELIST without an override practical.
* Touch up the comments
The following changes since commit f07045fcae859c902434062d1725f1348f42d1dd:
oeqa/oetest.py: add better package search for hasPackage() (2015-08-26 08:26:37 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/whitelist
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/whitelist
Paul Eggleton (1):
classes/whitelist: add class to allow whitelisting recipes from a
layer
meta/classes/whitelist.bbclass | 34 ++++++++++++++++++++++++++++++++++
1 file changed, 34 insertions(+)
create mode 100644 meta/classes/whitelist.bbclass
--
2.1.0
next reply other threads:[~2015-08-27 12:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 12:36 Paul Eggleton [this message]
2015-08-27 12:36 ` [PATCH v2 1/1] classes/whitelist: add class to allow whitelisting recipes from a layer Paul Eggleton
2015-08-28 6:07 ` Khem Raj
2015-08-28 8:34 ` Paul Eggleton
2015-08-28 13:09 ` Paul Eggleton
2015-08-28 15:11 ` Khem Raj
2015-08-28 13:55 ` Otavio Salvador
2015-08-28 14:00 ` Paul Eggleton
2015-08-28 14:09 ` Otavio Salvador
2015-08-28 14:19 ` Paul Eggleton
2015-08-28 17:32 ` Otavio Salvador
2015-08-28 8:28 ` [PATCH v2 0/1] Add recipe whitelisting class Patrick Ohly
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=cover.1440678731.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