From: "Bruce, Henry" <henry.bruce@intel.com>
To: "pab@pabigot.com" <pab@pabigot.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"paul.eggleton@linux.intel.com" <paul.eggleton@linux.intel.com>
Subject: Re: npm.bbclass support for deep native modules?
Date: Fri, 2 Dec 2016 19:10:41 +0000 [thread overview]
Message-ID: <1480705839.8273.22.camel@intel.com> (raw)
In-Reply-To: <f1da4624-99b2-46ec-a49d-892e2a491a8f@pabigot.com>
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 files generated by devtool don't include it.
> From the Wiki:
>
> "Devtool cannot detect native libraries in module dependencies, you
> you'll need to manually add packages to recipe"
>
> The Wiki doesn't go into detail of how that's supposed to be done. Is
> the existing infrastructure supposed to be able to find
> globally-installed modules?
I believe that this refers to native code depending on another native
library (e.g. libfoo). In this case, a package for libfoo would have to
be available and added to DEPENDS. This is not applicable for modern-
syslog. Paul - correct me if I've got this wrong.
> I'm wondering whether https://yarnpkg.com/ or one of the other nodejs
> dependency managers might be an alternative, as I believe npm's
> approach to dependencies is not suited to level of lockdown needed by
> Yocto and many other production systems.
Good idea, but we need to balance the complexity of adding another tool
vs. figuring this out with npm.
Back to the problem. I have re-created the statsd build failure, and
agree with your diagnosis, but don't have am immediate solution.
I have opened a bug #10760, and added you to CC list. Let's use this
bug to communicate from hereon.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10760
Henry
prev parent reply other threads:[~2016-12-02 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-27 0:17 npm.bbclass support for deep native modules? Peter A. Bigot
2016-11-28 10:11 ` Paul Eggleton
2016-11-28 10:35 ` Peter A. Bigot
2016-11-28 11:44 ` Jack Mitchell
2016-12-02 19:10 ` Bruce, Henry [this message]
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=1480705839.8273.22.camel@intel.com \
--to=henry.bruce@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pab@pabigot.com \
--cc=paul.eggleton@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox