Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Christopher Larson <kergoth@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Christopher Larson <chris_larson@mentor.com>
Subject: [PATCHv2 0/6] recipetool/devtool/oe-selftest: pull from BBPATH
Date: Mon, 20 Jul 2015 15:15:38 -0700	[thread overview]
Message-ID: <cover.1437430369.git.chris_larson@mentor.com> (raw)

From: Christopher Larson <chris_larson@mentor.com>

Ensures that recipetool and devtool pull plugins from layers, and
oe-selftest will pull tests from layers.

Unrelated to that, also prevents a traceback on parsing failure, and adds
a tiny feature to appendsrc to facilitate reuse by other sub-commands.

[v2 Update] `devtool: also load plugins from BBPATH` was fixed, so it no longer
breaks the devtool selftests.


The following changes since commit b283b82ec59a2137cf717811172765848fa813fa:

  core-image-lsb-sdk: use kernel-devsrc to ensure kernel module builds work (2015-07-20 10:39:02 +0100)

are available in the git repository at:

  git@github.com:kergoth/openembedded-core yocto-bug-7625

for you to fetch changes up to 35a9ce57747248192dc5c0dd7916e15e58a5835e:

  oe-selftest: add libdirs from BBPATH to sys.path (2015-07-20 15:11:59 -0700)

----------------------------------------------------------------
Christopher Larson (6):
      recipetool: catch BBHandledException from parsing
      recipetool.append: add extralines arg to appendsrc
      recipetool: also load plugins from BBPATH
      devtool: also load plugins from BBPATH
      oe-selftest: obey oeqa.selftest.__path__
      oe-selftest: add libdirs from BBPATH to sys.path

 scripts/devtool                  | 57 +++++++++++++++++++++++++---------------
 scripts/lib/devtool/__init__.py  |  4 +--
 scripts/lib/recipetool/append.py |  4 +--
 scripts/oe-selftest              | 18 +++++++++----
 scripts/recipetool               | 56 ++++++++++++++++++++++++---------------
 5 files changed, 88 insertions(+), 51 deletions(-)

-- 
2.2.1



             reply	other threads:[~2015-07-20 22:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-20 22:15 Christopher Larson [this message]
2015-07-20 22:15 ` [PATCHv2 1/6] recipetool: catch BBHandledException from parsing Christopher Larson
2015-07-20 22:15 ` [PATCHv2 2/6] recipetool.append: add extralines arg to appendsrc Christopher Larson
2015-07-20 22:15 ` [PATCHv2 3/6] recipetool: also load plugins from BBPATH Christopher Larson
2015-07-22 10:55   ` Paul Eggleton
2015-07-22 15:34     ` Christopher Larson
2015-07-20 22:15 ` [PATCHv2 4/6] devtool: " Christopher Larson
2015-07-22 11:02   ` Paul Eggleton
2015-07-22 15:36     ` Christopher Larson
2015-07-20 22:15 ` [PATCHv2 5/6] oe-selftest: obey oeqa.selftest.__path__ Christopher Larson
2015-07-20 22:15 ` [PATCHv2 6/6] oe-selftest: add libdirs from BBPATH to sys.path Christopher Larson
2015-07-22 11:02 ` [PATCHv2 0/6] recipetool/devtool/oe-selftest: pull from BBPATH Paul Eggleton
2015-07-22 15:29   ` Christopher Larson

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.1437430369.git.chris_larson@mentor.com \
    --to=kergoth@gmail.com \
    --cc=chris_larson@mentor.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