From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
enrico.scholz@sigma-chemnitz.de
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Error building an npm package: npmignore: not found
Date: Tue, 28 Jun 2022 18:44:47 +0200 [thread overview]
Message-ID: <d646b29d-e4e8-6ec0-9e8c-238f1dead305@bootlin.com> (raw)
In-Reply-To: <488fac057190a6378b550763fbcd1faaa9b22cce.camel@linuxfoundation.org>
Richard, Enrico,
On 6/27/22 18:47, Richard Purdie wrote:
> On Mon, 2022-06-27 at 18:37 +0200, Enrico Scholz via
> lists.openembedded.org wrote:
>> "Michael Opdenacker via lists.openembedded.org"
>> <michael.opdenacker=bootlin.com@lists.openembedded.org> writes:
>>
>>> I'm testing the Yocto Project Documentation for creating NPM packages
>> npm is broken since kirkstone; see
>> https://patchwork.yoctoproject.org/project/oe-core/list/?series=4303 for
>> patches.
>>
> Thanks for the reminder, we should probably test and merge these. I was
> hoping we'd get some review from someone else but it seems not many
> people are using those code paths :/.
Yessss, the changes now in Poky's master branch allowed me to build my
recipe and all issues are gone.
What the documentation describes still works.
Many thanks
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2022-06-28 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 16:19 Error building an npm package: npmignore: not found Michael Opdenacker
2022-06-27 16:37 ` [OE-core] " Enrico Scholz
2022-06-27 16:47 ` Richard Purdie
2022-06-28 16:44 ` Michael Opdenacker [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=d646b29d-e4e8-6ec0-9e8c-238f1dead305@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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