From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Broken NPM builds
Date: Thu, 27 Apr 2017 12:52:54 +0300 [thread overview]
Message-ID: <f58c1b82-bd35-b494-58f4-e6a7b2c2775c@linux.intel.com> (raw)
In-Reply-To: <CB34FC1D-AA6C-4C69-8C64-DF963214FFEB@nodefield.com>
On 04/26/2017 11:31 PM, Ilkka Myller wrote:
> This design allows building static, immutable, OE-proper packages for
> Node.js based applications while still using standard npm installation
> process on the build host. This is where OE core npm class differs the
> most by-design.
But are they reproducible? If the app is built one week later, is there
a guarantee that it will pull in the same components, and a check that
it is indeed so?
Also, are the licenses of various dependencies tracked and enforced?
> meta-nodejs has chosen not to promote non-standard use of npm utility,
> npm repository or npm installation process.
With this, I fully agree. I can only see pain and suffering with the
current oe-core approach.
Alex
next prev parent reply other threads:[~2017-04-27 9:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 16:01 Broken NPM builds Davis, Michael
2017-04-26 19:28 ` Trevor Woerner
2017-04-26 19:43 ` Davis, Michael
2017-04-26 20:31 ` Ilkka Myller
2017-04-27 9:52 ` Alexander Kanavin [this message]
2017-04-27 9:56 ` Alexander Kanavin
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=f58c1b82-bd35-b494-58f4-e6a7b2c2775c@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox