From: Ola x Nilsson <ola.x.nilsson@axis.com>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: "paul.eggleton@linux.intel.com" <paul.eggleton@linux.intel.com>
Subject: Re: [PATCH 0/4] Load devtool and reciptool plugins in a well-defined manner
Date: Tue, 6 Dec 2016 07:37:16 +0000 [thread overview]
Message-ID: <3d0139cbc58340fea6f0ea733004c06a@XBOX01.axis.com> (raw)
In-Reply-To: <1477393415-13053-1-git-send-email-olani@axis.com>
Ping?
--
Ola x Nilsson
> -----Original Message-----
> From: Ola x Nilsson [mailto:olani@axis.com]
> Sent: den 25 oktober 2016 13:04
> To: Ola x Nilsson; openembedded-core@lists.openembedded.org
> Subject: [PATCH 0/4] Load devtool and reciptool plugins in a well-defined
> manner
>
> From: Ola x Nilsson <ola.x.nilsson@axis.com>
>
> Make devtool and recipetool load plugins in a well-defined and expected
> manner.
>
> devtool and reciptool search for pluings first in scripts/lib/<tool> and then in
> BBPATH. Each found plugin is loaded, which means that any plugin found
> later in BBPATH shadows previously loaded plugins.
> plugin_init is loaded for all plugins, no matter whether they are later
> replaced. register_plugin is called once for each time a plugin with a certain
> name is found, but it is always called on the last loaded plugin.
>
> Change the scriptutils.load_plugins function to never load a plugin file if one
> with the same filename has already been loaded. This means that the first
> found plugin wins.
>
> Change the load order to first search BBPATH and then scripts/lib/tools. This
> means that plugins in scripts/lib/<tool> can be shadowed by plugins in layers.
>
> Ola x Nilsson (4):
> devtool: selftest: add test for devtool plugin loading
> recipetool: selftest: Add test for recipetool plugin loading
> devtool: Load plugins in a well defined order
> recipetool: Load plugins in a well defined order
>
> meta-selftest/lib/devtool/bbpath.py | 44
> ++++++++++++++++++++++++++++++++++
> meta-selftest/lib/recipetool/bbpath.py | 41
> +++++++++++++++++++++++++++++++
> meta/lib/oeqa/selftest/devtool.py | 43
> +++++++++++++++++++++++++++++++++
> meta/lib/oeqa/selftest/recipetool.py | 44
> ++++++++++++++++++++++++++++++++++
> scripts/devtool | 3 ++-
> scripts/lib/scriptutils.py | 8 +++++--
> scripts/recipetool | 4 ++--
> 7 files changed, 182 insertions(+), 5 deletions(-) create mode 100644 meta-
> selftest/lib/devtool/bbpath.py
> create mode 100644 meta-selftest/lib/recipetool/bbpath.py
>
> --
> 2.1.4
next prev parent reply other threads:[~2016-12-06 7:44 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 ` [PATCH 4/4] recipetool: " Ola x Nilsson
2016-12-06 7:37 ` Ola x Nilsson [this message]
2016-12-07 21:16 ` [PATCH 0/4] Load devtool and reciptool plugins in a well-defined manner 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=3d0139cbc58340fea6f0ea733004c06a@XBOX01.axis.com \
--to=ola.x.nilsson@axis.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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