From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Trevor Woerner <twoerner@gmail.com>,
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 23:13:26 +0000 [thread overview]
Message-ID: <1456701206.11498.174.camel@linuxfoundation.org> (raw)
In-Reply-To: <56D33008.9010306@gmail.com>
On Sun, 2016-02-28 at 12:36 -0500, Trevor Woerner wrote:
> On 02/28/16 12:09, Trevor Woerner wrote:
> > 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/recip
> > > es-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:
>
> Ah sorry. I needed bitbake's master-next.
There was a patch missing, bitbake master should be good now.
Cheers,
Richard
next prev parent reply other threads:[~2016-02-28 23:13 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
2016-02-28 17:36 ` Trevor Woerner
2016-02-28 23:13 ` Richard Purdie [this message]
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=1456701206.11498.174.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=brendan.le.foll@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=twoerner@gmail.com \
/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.