From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Stefan Herbrechtsmeier <stefan.herbrechtsmeier-oss@weidmueller.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
Jasper Orschulko <Jasper.Orschulko@iris-sensing.com>,
"jeanmarie.lemetayer@gmail.com" <jeanmarie.lemetayer@gmail.com>,
"bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>,
"martin@mko.dev" <martin@mko.dev>,
Daniel Baumgart <Daniel.Baumgart@iris-sensing.com>
Subject: Re: [bitbake-devel] Improving npm(sw) fetcher & integration within Bitbake
Date: Mon, 8 Nov 2021 08:59:40 +0100 [thread overview]
Message-ID: <CANNYZj8=w5WZ50=thLn_c+DQDyTqd9j_C_m0j_WdTewi+Upt3w@mail.gmail.com> (raw)
In-Reply-To: <6c13452e-77cc-6cd5-8d3d-0e2128663286@weidmueller.com>
[-- Attachment #1: Type: text/plain, Size: 649 bytes --]
On Mon, 8 Nov 2021 at 08:41, Stefan Herbrechtsmeier <
stefan.herbrechtsmeier-oss@weidmueller.com> wrote:
> > Also, I did realise the npm fetcher tests simply don't work anymore.
> They're not
> > run as standard as our infrastructure didn't have npm on it to run the
> tests so
> > they have bitrotted :(.
>
> Is it possible to add the nodejs recipe to the core?
>
I don't think it's eligible (the criteria for core is 'broadly useful for
embedded use cases', which nodejs is clearly not ;). I think the question
should be 'is it possible to run nodejs tests on the autobuilder so it
doesn't regress', and to that the answer is 'yes'.
Alex
Alex
[-- Attachment #2: Type: text/html, Size: 1213 bytes --]
next prev parent reply other threads:[~2021-11-08 7:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 12:29 Improving npm(sw) fetcher & integration within Bitbake Jasper Orschulko
2021-11-04 13:09 ` [bitbake-devel] " Alexander Kanavin
2021-11-06 16:58 ` Mike Crowe
2021-11-08 8:01 ` Stefan Herbrechtsmeier
2021-11-08 12:44 ` Jasper Orschulko
2021-11-11 7:51 ` Stefan Herbrechtsmeier
2021-11-04 23:15 ` Richard Purdie
2021-11-05 9:07 ` Stefan Herbrechtsmeier
2021-11-05 11:24 ` Jean-Marie Lemetayer
2021-11-05 16:02 ` Jasper Orschulko
2021-11-05 17:42 ` Alexander Kanavin
[not found] ` <5fb67154d576b74629e4836a86dcb5e479b73e67.camel@linuxfoundation.org>
2021-11-06 10:30 ` Konrad Weihmann
2021-11-08 7:41 ` Stefan Herbrechtsmeier
2021-11-08 7:59 ` Alexander Kanavin [this message]
[not found] ` <4106f9ef-5b2e-5276-f1bb-c80a989d7fdf@mko.dev>
2021-11-05 11:12 ` Martin Koppehel
2021-11-05 13:16 ` Stefan Herbrechtsmeier
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='CANNYZj8=w5WZ50=thLn_c+DQDyTqd9j_C_m0j_WdTewi+Upt3w@mail.gmail.com' \
--to=alex.kanavin@gmail.com \
--cc=Daniel.Baumgart@iris-sensing.com \
--cc=Jasper.Orschulko@iris-sensing.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=jeanmarie.lemetayer@gmail.com \
--cc=martin@mko.dev \
--cc=richard.purdie@linuxfoundation.org \
--cc=stefan.herbrechtsmeier-oss@weidmueller.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.