From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 00/13] devtool / recipetool fixes
Date: Thu, 31 Aug 2017 11:54:04 +1200 [thread overview]
Message-ID: <cover.1504137086.git.paul.eggleton@linux.intel.com> (raw)
Some fixes for devtool / recipetool issues, along with a couple of
related changes to the oe-selftest tests. I have run the oe-selftest
tests for devtool and recipetool and they pass with these changes
applied.
NOTE: this patchset depends upon the bitbake patchset I just sent to the
bitbake-devel list.
The following changes since commit 62f1122ef166eba56441d669c6b3b3fe5f367418:
bluez5: cosmetic fixes to bluetooth bootscript (2017-08-30 11:13:52 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/devtool29-oe
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=paule/devtool29-oe
Paul Eggleton (12):
devtool: update-recipe: ensure patches get deleted in srcrev mode
devtool: upgrade: fix handling of non-absolute paths
devtool: upgrade: workaround for recipes which apply patches conditional upon class
devtool: edit-recipe: fix regression
oe-selftest: devtool: test find-recipe and edit-recipe
devtool: add: add explicit srcrev/branch options
recipetool: create: make recently added branch/tag handling git specific
recipetool: create: fix SRCPV prefix for non-git SCMs
recipetool: create: suppress npm shrinkwrap/lockdown warnings again
recipetool: create: detect Eclipse licenses
oe-selftest: tinfoil: add a test for variable history
scriptutils: fix fetch_url() to use lowercase dummy recipe name
paul (1):
devtool: upgrade: check that user has configured git properly
meta/lib/oe/recipeutils.py | 43 +++++++++++++++++++++++-------
meta/lib/oeqa/selftest/cases/devtool.py | 25 ++++++++++++------
meta/lib/oeqa/selftest/cases/tinfoil.py | 34 ++++++++++++++++++++++++
scripts/lib/devtool/standard.py | 20 +++++++++++---
scripts/lib/devtool/upgrade.py | 32 ++++++++++++++++++++--
scripts/lib/devtool/utilcmds.py | 15 ++++++++---
scripts/lib/recipetool/create.py | 47 ++++++++++++++++++++++++++++-----
scripts/lib/scriptutils.py | 2 +-
8 files changed, 183 insertions(+), 35 deletions(-)
--
2.9.5
next reply other threads:[~2017-08-30 23:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 23:54 Paul Eggleton [this message]
2017-08-30 23:54 ` [PATCH 01/13] devtool: update-recipe: ensure patches get deleted in srcrev mode Paul Eggleton
2017-08-30 23:54 ` [PATCH 02/13] devtool: upgrade: fix handling of non-absolute paths Paul Eggleton
2017-08-30 23:54 ` [PATCH 03/13] devtool: upgrade: check that user has configured git properly Paul Eggleton
2017-08-31 13:29 ` Burton, Ross
2017-08-31 21:01 ` Paul Eggleton
2017-08-30 23:54 ` [PATCH 04/13] devtool: upgrade: workaround for recipes which apply patches conditional upon class Paul Eggleton
2017-08-30 23:54 ` [PATCH 05/13] devtool: edit-recipe: fix regression Paul Eggleton
2017-08-30 23:54 ` [PATCH 06/13] oe-selftest: devtool: test find-recipe and edit-recipe Paul Eggleton
2017-08-30 23:54 ` [PATCH 07/13] devtool: add: add explicit srcrev/branch options Paul Eggleton
2017-08-30 23:54 ` [PATCH 08/13] recipetool: create: make recently added branch/tag handling git specific Paul Eggleton
2017-08-30 23:54 ` [PATCH 09/13] recipetool: create: fix SRCPV prefix for non-git SCMs Paul Eggleton
2017-08-30 23:54 ` [PATCH 10/13] recipetool: create: suppress npm shrinkwrap/lockdown warnings again Paul Eggleton
2017-08-30 23:54 ` [PATCH 11/13] recipetool: create: detect Eclipse licenses Paul Eggleton
2017-08-30 23:54 ` [PATCH 12/13] oe-selftest: tinfoil: add a test for variable history Paul Eggleton
2017-08-30 23:54 ` [PATCH 13/13] scriptutils: fix fetch_url() to use lowercase dummy recipe name 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.1504137086.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.