From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] devtool / recipetool fixes for node.js modules
Date: Wed, 12 Apr 2017 22:41:25 +1200 [thread overview]
Message-ID: <cover.1491993601.git.paul.eggleton@linux.intel.com> (raw)
This fixes a few regressions in master in handling devtool add on
node.js modules relative to morty.
The following changes since commit 210c518ba8f8d6ec6e9d34e0df8b963a3b2e0593:
ptest-runner: Upgrade to minor version 2.0.2 (2017-04-11 18:09:21 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/npm-fixes3
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=paule/npm-fixes3
Paul Eggleton (4):
recipetool: create: fix for regression in npm license handling
devtool: add: fix node.js/npm handling with recipe specific sysroots
devtool: add: prevent repeatedly running recipetool
recipetool: create: hide missing npm error when called from devtool
scripts/lib/devtool/__init__.py | 25 ++++++++++++++-----------
scripts/lib/devtool/standard.py | 6 +++++-
scripts/lib/recipetool/create.py | 32 ++++++++++++++++++++++++++------
scripts/lib/recipetool/create_npm.py | 23 +++++++++++++----------
4 files changed, 58 insertions(+), 28 deletions(-)
--
2.9.3
next reply other threads:[~2017-04-12 10:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 10:41 Paul Eggleton [this message]
2017-04-12 10:41 ` [PATCH 1/4] recipetool: create: fix for regression in npm license handling Paul Eggleton
2017-04-12 10:41 ` [PATCH 2/4] devtool: add: fix node.js/npm handling with recipe specific sysroots Paul Eggleton
2017-04-12 10:41 ` [PATCH 3/4] devtool: add: prevent repeatedly running recipetool Paul Eggleton
2017-04-12 10:41 ` [PATCH 4/4] recipetool: create: hide missing npm error when called from devtool 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.1491993601.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox