From: "António Oliveira" <antonio@amsobr.com>
To: yocto@lists.yoctoproject.org
Cc: "António Oliveira" <antonio@amsobr.com>
Subject: [RFC PATCH 0/1] lts mixin: kirkstone/nodejs proposal
Date: Mon, 4 Dec 2023 18:30:54 +0000 [thread overview]
Message-ID: <20231204183055.29931-1-antonio@amsobr.com> (raw)
Hi all,
This patch contains my proposal for an mixin layer that adds nodejs v18
and v20 to kirkstone.
Kirkstone ships with nodejs-16, whose maintenance window ended in
October 2023 (a).
Kirkstone will be supported until April 2026 and it would be nice to have
some level of support for a maintained version of nodejs during that time
window.
This proposal seeks to address that by adding nodejs-18 and nodejs-20,
which will be maintained until April 2025 and 2026, respectively.
The recipes for nodejs-18 are taken from Mickledore and the recipes for
nodejs-20 from master.
The variable NODE_VERSION can be ser in local.conf to choose either v18
or v20 (the default).
This is my first attempt at sending a patch upstream with git send-email
so any comments or suggestions for improvement are welcome. That's also
the reason why I marked this as an RFC.
Cheers,
António
António Oliveira (1):
initial commit
--
2.34.1
next reply other threads:[~2023-12-04 18:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 18:30 António Oliveira [this message]
2023-12-04 18:30 ` [RFC PATCH 1/1] initial commit António Oliveira
2023-12-05 10:32 ` [yocto] " Jose Quaresma
2023-12-05 18:21 ` António Oliveira
2023-12-05 10:44 ` [yocto] [RFC PATCH 0/1] lts mixin: kirkstone/nodejs proposal Jose Quaresma
2023-12-05 18:26 ` António Oliveira
2023-12-07 11:07 ` Jose Quaresma
2024-01-08 15:58 ` [RFC PATCH v2 0/3] " António Oliveira
2024-01-08 15:58 ` [RFC PATCH v2 1/3] initial commit: license, readme, conf António Oliveira
2024-01-08 15:58 ` [RFC PATCH v2 2/3] add nodejs-18 from mickledore António Oliveira
2024-01-08 15:58 ` [RFC PATCH v2 3/3] add layer configuration for default node António Oliveira
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=20231204183055.29931-1-antonio@amsobr.com \
--to=antonio@amsobr.com \
--cc=yocto@lists.yoctoproject.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;
as well as URLs for NNTP newsgroup(s).