From: Ola x Nilsson <ola.x.nilsson@axis.com>
To: olani@axis.com, openembedded-core@lists.openembedded.org
Subject: [PATCH 4/4] recipetool: Load plugins in a well defined order
Date: Tue, 25 Oct 2016 13:03:35 +0200 [thread overview]
Message-ID: <1477393415-13053-5-git-send-email-olani@axis.com> (raw)
In-Reply-To: <1477393415-13053-1-git-send-email-olani@axis.com>
From: Ola x Nilsson <ola.x.nilsson@axis.com>
To allow recipetool plugins in one layer to shadow another in a well
defined way, first search BBPATH/lib/recipetool directories and then
scripts/lib/recipetool and load only the first found.
The previous search and load loop would load all found plugins with the
ones found later replacing any found before.
Signed-off-by: Ola x Nilsson <ola.x.nilsson@axis.com>
---
scripts/recipetool | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/recipetool b/scripts/recipetool
index 1052cd2..00c9007 100755
--- a/scripts/recipetool
+++ b/scripts/recipetool
@@ -78,8 +78,8 @@ def main():
tinfoil = tinfoil_init(False)
try:
- for path in ([scripts_path] +
- tinfoil.config_data.getVar('BBPATH', True).split(':')):
+ for path in (tinfoil.config_data.getVar('BBPATH', True).split(':')
+ + [scripts_path]):
pluginpath = os.path.join(path, 'lib', 'recipetool')
scriptutils.load_plugins(logger, plugins, pluginpath)
--
2.1.4
next prev parent reply other threads:[~2016-10-25 11:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 11:03 [PATCH 0/4] Load devtool and reciptool plugins in a well-defined manner Ola x Nilsson
2016-10-25 11:03 ` [PATCH 1/4] devtool: selftest: add test for devtool plugin loading Ola x Nilsson
2016-10-25 11:03 ` [PATCH 2/4] recipetool: selftest: Add test for recipetool " Ola x Nilsson
2016-10-25 11:03 ` [PATCH 3/4] devtool: Load plugins in a well defined order Ola x Nilsson
2016-10-25 11:03 ` Ola x Nilsson [this message]
2016-12-06 7:37 ` [PATCH 0/4] Load devtool and reciptool plugins in a well-defined manner Ola x Nilsson
2016-12-07 21:16 ` Paul Eggleton
2016-12-08 15:24 ` Burton, Ross
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=1477393415-13053-5-git-send-email-olani@axis.com \
--to=ola.x.nilsson@axis.com \
--cc=olani@axis.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