From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/6] npm fetcher fixes
Date: Tue, 6 Sep 2016 10:57:27 +1200 [thread overview]
Message-ID: <cover.1473116117.git.paul.eggleton@linux.intel.com> (raw)
Some fixes for issues in the npm fetcher that I found while trying to
implement support for non-npm node.js source trees.
The following changes since commit dc756510a95f88b192352be6fcd1d5d77852c348:
bb.fetch2.svn: correctly pass workdir when fetching (2016-09-02 16:29:36 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib paule/bb-npm-fixes3
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/bb-npm-fixes3
Paul Eggleton (6):
fetch2/npm: explicitly specify workdir
fetch2/npm: fix broken fetches if more than one npm URL fetched
fetch2/npm: support subdir= parameter
fetch2/npm: handle top-level shrinkwrap file
fetch2/npm: clarify comment
lib/bb/utils: edit_metadata() comment tweaks
lib/bb/fetch2/npm.py | 29 +++++++++++++++++++++--------
lib/bb/utils.py | 4 +++-
2 files changed, 24 insertions(+), 9 deletions(-)
--
2.5.5
next reply other threads:[~2016-09-05 22:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 22:57 Paul Eggleton [this message]
2016-09-05 22:57 ` [PATCH 1/6] fetch2/npm: explicitly specify workdir Paul Eggleton
2016-09-05 22:57 ` [PATCH 2/6] fetch2/npm: fix broken fetches if more than one npm URL fetched Paul Eggleton
2016-09-05 22:57 ` [PATCH 3/6] fetch2/npm: support subdir= parameter Paul Eggleton
2016-09-05 22:57 ` [PATCH 4/6] fetch2/npm: handle top-level shrinkwrap file Paul Eggleton
2016-09-05 22:57 ` [PATCH 5/6] fetch2/npm: clarify comment Paul Eggleton
2016-09-05 22:57 ` [PATCH 6/6] lib/bb/utils: edit_metadata() comment tweaks 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.1473116117.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=bitbake-devel@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.