From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/2] A couple of devtool fixes
Date: Thu, 14 Sep 2017 16:15:10 +1200 [thread overview]
Message-ID: <cover.1505361895.git.paul.eggleton@linux.intel.com> (raw)
A fix for devtool modify and other source extracting subcommands to
handle dependencies, and a fix for devtool modify within the eSDK.
NOTE: the patch I just sent to the bitbake list to fix a bug in the way
empty directory notifications should be merged prior to merging this
series.
Changes since v1:
* Drop the invalidateParseCache command call since I have sent a fix
for the bug that caused it to be required.
The following changes since commit 2ebbeb61114e4b847e9164c621ac87b5cf03a299:
staging: gracefully abort if two recipes conflict in the sysroot (2017-09-11 17:30:15 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/devtool30-oe
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=paule/devtool30-oe
Paul Eggleton (2):
devtool: rework source extraction so that dependencies are handled
devtool: ensure recipes devtool is working on are unlocked within the eSDK
meta/classes/devtool-source.bbclass | 165 ++++++++++++++++++++++++
meta/classes/populate_sdk_ext.bbclass | 3 +
meta/classes/sstate.bbclass | 9 +-
meta/lib/oeqa/selftest/cases/devtool.py | 10 +-
scripts/devtool | 20 ---
scripts/lib/devtool/__init__.py | 40 ++++++
scripts/lib/devtool/standard.py | 217 ++++++++++----------------------
scripts/lib/devtool/upgrade.py | 9 +-
8 files changed, 295 insertions(+), 178 deletions(-)
create mode 100644 meta/classes/devtool-source.bbclass
--
2.9.5
next reply other threads:[~2017-09-14 4:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 4:15 Paul Eggleton [this message]
2017-09-14 4:15 ` [PATCH v2 1/2] devtool: rework source extraction so that dependencies are handled Paul Eggleton
2017-09-14 4:24 ` Paul Eggleton
2017-09-14 4:15 ` [PATCH v2 2/2] devtool: ensure recipes devtool is working on are unlocked within the eSDK Paul Eggleton
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.1505361895.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 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.