From: Trevor Woerner <twoerner@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
brendan.le.foll@intel.com,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] npm.bbclass: Add npm class to match fetcher
Date: Sun, 28 Feb 2016 12:09:09 -0500 [thread overview]
Message-ID: <56D329B5.5090101@gmail.com> (raw)
In-Reply-To: <1456648351.11498.130.camel@linuxfoundation.org>
On 02/28/16 03:32, Richard Purdie wrote:
> On Sat, 2016-02-27 at 19:53 -0500, Trevor Woerner wrote:
>> On 02/25/16 10:06, brendan.le.foll@intel.com wrote:
>>> npm class supports the npm fetcher, helping doing the basic
>>> compile/install
>>> stages of an npm package
>> Any chance you might have an npm recipe example? Maybe something like
>> express?
> Not express but there are some in:
>
> https://github.com/arfoll/meta-brendan-nodepkgs/tree/master/recipes-node
Thanks!
I guess I don't have enough "plumbing" quite yet. I have all the master
branches of everything I need and I cherry picked Brendan's npm.bbclass
but I still get:
$ bitbake forever
ERROR: ExpansionError during parsing
/z/layerindex-master/layers/meta-brendan-nodepkgs/recipes-node/once/once_1.3.3.bb:
Failure expanding variable do_fetch[file-checksums], expression was
${@bb.fetch.get_checksum_file_list(d)} ${@get_lic_checksum_file_list(d)}
which triggered exception NoMethodError: Could not find a fetcher which
supports the URL: 'npm://registry.npmjs.org;name=once;version=1.3.3'
I'm not sure if this error is complaining about a fetcher issue (which I
can't figure out because bitbake does have the commits with support for
npm://) or a license/checksum error.
next prev parent reply other threads:[~2016-02-28 17:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 15:06 [PATCH] npm.bbclass: Add npm class to match fetcher brendan.le.foll
2016-02-28 0:53 ` Trevor Woerner
2016-02-28 8:32 ` Richard Purdie
2016-02-28 17:09 ` Trevor Woerner [this message]
2016-02-28 17:36 ` Trevor Woerner
2016-02-28 23:13 ` Richard Purdie
2016-02-29 3:23 ` Trevor Woerner
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=56D329B5.5090101@gmail.com \
--to=twoerner@gmail.com \
--cc=brendan.le.foll@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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