From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
openembedded-core@lists.openembedded.org
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: Fun with npm shrinkwrap
Date: Wed, 7 Jun 2017 14:43:39 +0300 [thread overview]
Message-ID: <615663ca-d13f-9bca-6e3d-e5dc22cfaebf@linux.intel.com> (raw)
In-Reply-To: <af72aeb2-915e-0c63-60e9-18b6c7bce5ad@siemens.com>
On 06/06/2017 06:14 PM, Jan Kiszka wrote:
> Yeah, good points. Probably this problem is also related to OE
> reimplementing parts of the npm logic.
>
> But I suppose those concepts won't materialize very soon, will they? I'm
> also looking for a short-term solution, at least some reasonable tactic
> to generate such recipes in the meantime. Is there something in that
> thread I should dig into?
What I am getting at is that it would be awesome if you convince your
management that npm support in Yocto is a problem that needs a better
solution and work on it. Yes, this means you can't work on product
development for quite some time; this is the price for using open source
projects without a commercial support contract :)
My apologies if this is not the answer you were seeking.
Alex
next prev parent reply other threads:[~2017-06-07 11:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 10:17 Fun with npm shrinkwrap Jan Kiszka
2017-06-06 14:12 ` Alexander Kanavin
2017-06-06 15:14 ` Jan Kiszka
2017-06-07 11:43 ` Alexander Kanavin [this message]
2017-06-07 12:04 ` Jan Kiszka
2017-06-07 14:09 ` Davis, Michael
2017-06-07 18:32 ` Jan Kiszka
2017-06-07 19:51 ` Davis, Michael
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=615663ca-d13f-9bca-6e3d-e5dc22cfaebf@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=jan.kiszka@siemens.com \
--cc=openembedded-core@lists.openembedded.org \
--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 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.