From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Christopher Larson <chris_larson@mentor.com>,
"bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Cc: "Eggleton, Paul" <paul.eggleton@intel.com>
Subject: Re: [RFC master][PATCH 4/4] bitbake-layers: convert to plugin-based
Date: Fri, 13 May 2016 00:20:54 +0100 [thread overview]
Message-ID: <1463095254.9746.61.camel@linuxfoundation.org> (raw)
In-Reply-To: <CABcZAN=Fmp0rTvVy9sEifLqHRtR0dDnsPox5xvmksww7aPop3Q@mail.gmail.com>
On Thu, 2016-05-12 at 16:12 -0700, Christopher Larson wrote:
> On Sat, Apr 30, 2016 at 12:41 PM, Christopher Larson <
> kergoth@gmail.com> wrote:
> > From: Christopher Larson <chris_larson@mentor.com>
> >
> > This uses bb.utils.load_plugins, based on the plugin handling in
> > recipetool
> > and devtool in oe-core.
> >
> > Signed-off-by: Christopher Larson <chris_larson@mentor.com>
> > ---
> > bin/bitbake-layers | 1065 ++----------------------
> > ------------
> > bitbake/lib/bblayers/__init__.py | 2 +
> > bitbake/lib/bblayers/action.py | 233 ++++++++
> > bitbake/lib/bblayers/common.py | 33 ++
> > bitbake/lib/bblayers/layerindex.py | 270 +++++++++
> > bitbake/lib/bblayers/query.py | 499 +++++++++++++++++
> > 6 files changed, 1097 insertions(+), 1005 deletions(-)
> > create mode 100644 bitbake/lib/bblayers/__init__.py
> > create mode 100644 bitbake/lib/bblayers/action.py
> > create mode 100644 bitbake/lib/bblayers/common.py
> > create mode 100644 bitbake/lib/bblayers/layerindex.py
> > create mode 100644 bitbake/lib/bblayers/query.py
> >
> Was this patch not applied for a specific reason, or just needs more
> time for review, or waiting until after python3 is merged?
The other pieces were straightforward so I merged them. I meant to ask
Paul for an Acked-by on this piece as he'd done more work on the plugin
based tools than I have but then I got distracted, sorry. Paul is
cc'd...
Cheers,
Richard
next prev parent reply other threads:[~2016-05-12 23:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1462041562.git.chris_larson@mentor.com>
2016-04-30 19:40 ` [RFC master][PATCH 1/4] bb.utils: add load_plugins from scriptutils Christopher Larson
2016-04-30 19:40 ` [RFC master][PATCH 2/4] bb.utils: use imp.get_suffixes for load_plugins Christopher Larson
2016-04-30 19:40 ` [RFC master][PATCH 3/4] bb.utils: let loaded plugins provide a plugin object Christopher Larson
2016-04-30 19:41 ` [RFC master][PATCH 4/4] bitbake-layers: convert to plugin-based Christopher Larson
2016-05-12 23:12 ` Christopher Larson
2016-05-12 23:20 ` Richard Purdie [this message]
2016-05-12 23:22 ` Christopher Larson
2016-05-16 21:02 ` Paul Eggleton
2016-05-16 22:06 ` Richard Purdie
2016-05-16 22:36 ` Christopher Larson
2016-05-17 14:52 ` 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=1463095254.9746.61.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=chris_larson@mentor.com \
--cc=paul.eggleton@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.