From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/8] recipetool create improvements
Date: Wed, 9 Mar 2016 17:48:47 +1300 [thread overview]
Message-ID: <cover.1457498464.git.paul.eggleton@linux.intel.com> (raw)
Changes since v1:
* Set PKGV and SUMMARY per package for split npm packages so they get
the values appropriate to the module they contain. PKGV is
particularly important so that the image manifests have the
appropriate version for each module.
* Create shrinkwrap/lockdown files next to npm recipes and add
references to them within the recipe
* Don't fail if license value in an npm module's package.json isn't a
simple string (more complicated license definitions are allowed
according to the npm documentation).
The following changes since commit 0d02159c8d66bb136f7da2c10fda7d1a57f40cec:
image.bbclass: fix incomplete .rootfs customization (2016-03-07 22:01:16 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/recipetool3
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/recipetool3
Paul Eggleton (8):
recipetool: create: be more tolerant of spacing in configure.ac
recipetool: create: improve mapping for autotools program macros
recipetool: create: match *LICENSE* as a license file
recipetool: create: add license file crunching
recipetool: create: split npm module dependencies into packages
recipetool: create: check if npm available if npm:// URL specified
recipetool: create: support creation of additional files by plugins
recipetool: create: shrinkwrap and lockdown npm modules
meta/classes/npm.bbclass | 20 ++++
meta/lib/oe/package.py | 32 +++++++
scripts/lib/devtool/standard.py | 6 +-
scripts/lib/recipetool/create.py | 146 +++++++++++++++++++++++++++++-
scripts/lib/recipetool/create_buildsys.py | 54 ++++++++---
scripts/lib/recipetool/create_npm.py | 114 ++++++++++++++++++++++-
6 files changed, 349 insertions(+), 23 deletions(-)
--
2.5.0
next reply other threads:[~2016-03-09 4:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 4:48 Paul Eggleton [this message]
2016-03-09 4:48 ` [PATCH v2 1/8] recipetool: create: be more tolerant of spacing in configure.ac Paul Eggleton
2016-03-09 4:48 ` [PATCH v2 2/8] recipetool: create: improve mapping for autotools program macros Paul Eggleton
2016-03-09 4:48 ` [PATCH v2 3/8] recipetool: create: match *LICENSE* as a license file Paul Eggleton
2016-03-09 4:48 ` [PATCH v2 4/8] recipetool: create: add license file crunching Paul Eggleton
2016-03-09 4:48 ` [PATCH v2 5/8] recipetool: create: split npm module dependencies into packages Paul Eggleton
2016-03-09 4:48 ` [PATCH v2 6/8] recipetool: create: check if npm available if npm:// URL specified Paul Eggleton
2016-03-09 4:48 ` [PATCH v2 7/8] recipetool: create: support creation of additional files by plugins Paul Eggleton
2016-03-09 4:48 ` [PATCH v2 8/8] recipetool: create: shrinkwrap and lockdown npm modules 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.1457498464.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