From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: nodejs: merge with nodejs-lts
Date: Sat, 03 Jun 2023 21:47:17 +0200 [thread overview]
Message-ID: <20230603194717.RTlL0bT-egginBi4KYJTueYl3r42pNQ24CiqPnuDmlU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40106@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1811 bytes --]
There's a closed pull request on the void-packages repository
nodejs: merge with nodejs-lts
https://github.com/void-linux/void-packages/pull/40106
Description:
Nodejs versioning says that every even release (12, 14, 16, 18) is an LTS release. The `nodejs` package currently uses version 16 which is a supported LTS version, `nodejs-lts` uses version 12 which is EOL and very old. Many packages use nodejs-lts for building, but then depend on the nodejs virtual package which defaults to nodejs, many packages don't work with old nodejs-lts and people couldn't have both installed. If we need to, we can always split nodejs-lts again, but right now I don't see a reason to do so. Alpine merged their nodejs-lts package to nodejs and provides nodejs-current for the latest version for development.
TODO:
- [x] fix chronograf build with nodejs 16 (probably with an update)
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
next prev parent reply other threads:[~2023-06-03 19:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 13:46 [PR PATCH] nodejs: update to 16.18.0, " paper42
2022-11-20 18:48 ` [PR PATCH] [Updated] " paper42
2022-11-25 20:21 ` nodejs: " leahneukirchen
2022-12-07 8:02 ` [PR PATCH] [Updated] " paper42
2022-12-15 17:12 ` akierig
2022-12-15 17:14 ` akierig
2022-12-15 19:11 ` [PR PATCH] [Updated] " paper42
2022-12-18 11:08 ` paper42
2023-02-04 16:36 ` dkwo
2023-02-04 17:07 ` paper42
2023-02-04 17:08 ` paper42
2023-02-04 17:43 ` dkwo
2023-03-01 20:22 ` paper42
2023-03-07 0:16 ` dkwo
2023-03-07 6:40 ` paper42
2023-03-07 16:50 ` dkwo
2023-05-16 14:41 ` dkwo
2023-06-02 19:18 ` [PR PATCH] [Updated] " paper42
2023-06-02 19:20 ` paper42
2023-06-03 19:47 ` paper42 [this message]
2023-06-03 19:47 ` paper42
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=20230603194717.RTlL0bT-egginBi4KYJTueYl3r42pNQ24CiqPnuDmlU@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).