On Mon, 2016-11-28 at 04:35 -0600, Peter A. Bigot wrote:
Hi Peter,
I'm helping Paul with this. Sadly, I'm not much of an npm expert
either, but want to improve support for node.js development.
>
> Sorry, that wasn't clear. statsd depends on modern-syslog but the
> lockdown and shrinkwrap
On 28/11/16 10:35, Peter A. Bigot wrote:
On 11/28/2016 04:11 AM, Paul Eggleton wrote:
Hi Peter,
On Sat, 26 Nov 2016 18:17:48 Peter A. Bigot wrote:
I'm using the current head of morty and trying to get a handle on the
new nodejs support in OE.
I'm failing to build a recipe for statsd.
On 11/28/2016 04:11 AM, Paul Eggleton wrote:
Hi Peter,
On Sat, 26 Nov 2016 18:17:48 Peter A. Bigot wrote:
I'm using the current head of morty and trying to get a handle on the
new nodejs support in OE.
I'm failing to build a recipe for statsd. Starting with this:
devtool add
Hi Peter,
On Sat, 26 Nov 2016 18:17:48 Peter A. Bigot wrote:
> I'm using the current head of morty and trying to get a handle on the
> new nodejs support in OE.
>
> I'm failing to build a recipe for statsd. Starting with this:
>
> devtool add
I'm using the current head of morty and trying to get a handle on the
new nodejs support in OE.
I'm failing to build a recipe for statsd. Starting with this:
devtool add 'npm://registry.npmjs.org;name=statsd;version=0.8.0'
bitbake statsd
produces an error related to the modern-syslog
On 17 August 2016 at 13:40, Paul Eggleton wrote:
> Hey Chris, long time!
>
Hey :)
> On Wed, 17 Aug 2016 11:11:13 Brendan Le Foll wrote:
> > >- Is there a reason to split the package like it does? Node projects
> > >tend to have huge dependency trees, it makes
Hey Chris, long time!
On Wed, 17 Aug 2016 11:11:13 Brendan Le Foll wrote:
> >- Is there a reason to split the package like it does? Node projects
> >tend to have huge dependency trees, it makes updating and distributing
> >node-based applications a bit of a chore if they end up split
On Tue, Aug 16, 2016 at 05:41:28PM +0100, Christopher Lord wrote:
>I've been using npm.bbclass with various node projects we're working on
>in the Connected Devices team at Mozilla, and had some
>questions/comments about behaviour (note that I'm basing this off of
>ostro master,
On 16 August 2016 at 17:41, Christopher Lord wrote:
> - Any patches end up getting packaged because they get put in the srcdir.
> I'm guessing this isn't intentional (or maybe it is?)
>
This isn't intentional - I've love to move the patches out of ${S} but
that's non-trivial
I've been using npm.bbclass with various node projects we're working on in
the Connected Devices team at Mozilla, and had some questions/comments
about behaviour (note that I'm basing this off of ostro master, which I
unfortunately have to use as no other Intel Edison bsp is adequate);
- Is there
10 matches
Mail list logo