From: Maxime Devos <maximedevos@telenet.be>
To: Attila Lendvai <attila@lendvai.name>,
"53414@debbugs.gnu.org" <53414@debbugs.gnu.org>
Subject: [bug#53414] [PATCH] update Node LTS to 16.13.2
Date: Fri, 25 Feb 2022 16:59:24 +0100 [thread overview]
Message-ID: <079ca956e4d7c6b71921ee34638de012ae0a0c5f.camel@telenet.be> (raw)
In-Reply-To: <sd9Oi7dJHu-Htzpw-2nTg6xUR2n84wErt6gEOc11sW5xV7e1PMvWS64IrH7SWDBBFqe8Xy8QLzvlSApQ2mzRdgPvaK6woyqnW9tNDS1Gvso=@lendvai.name>
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
Attila Lendvai schreef op vr 25-02-2022 om 13:09 [+0000]:
> > Still, the latest LTS (v16) seems better to me since it is newer
> > and will be
> > supported for longer.
>
> with packages like nodejs one often needs both older and newer
> versions in
> parallel to also be able to build projects that haven't been ported
> to the new
> nodejs.
Ignoring bootstrapping, this does not seem to be the case so far in
Guix -- the only results of "git grep -F \#\:node gnu" is
# 7 lines
gnu/packages/node.scm: `(#:node ,node-bootstrap
so it seems that, except for bootstrapping, a single version of 'node'
suffices.
If it turns out that some packages still require v14, then we can
discuss that upstream, patch the package and/or introduce a 'node-14'
package variant, like we do with, say, autoconf, bcftools and gcc.
Actually 'gcc' does not point to the latest version, but to the
slightly older 10.3.0, but that's only due to core-updates concerns
and perhaps because upstream does -Werror too often. And 'autoconf'
is not autoconf-2.71 because ‘this is the renaissance version, which is
not widelt supported yet’. But AFAICT, there are no compatibility
concerns with v14->v16.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-02-25 16:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 15:11 [bug#53414] [PATCH] update Node LTS to 16.13.2 zamfofex
2022-02-23 13:13 ` code
2022-02-25 11:07 ` Maxime Devos
2022-02-25 11:24 ` code
2022-02-25 12:38 ` Maxime Devos
2022-02-25 13:09 ` Attila Lendvai
2022-02-25 15:59 ` Maxime Devos [this message]
2022-02-25 16:31 ` Pierre Langlois
2022-02-25 17:22 ` Maxime Devos
2022-05-02 6:10 ` Ryan Sundberg via Guix-patches via
2022-05-15 13:45 ` Pierre Langlois
2022-06-09 6:39 ` Ryan Sundberg via Guix-patches via
2022-06-09 20:49 ` Maxime Devos
2022-06-09 20:50 ` Maxime Devos
2022-06-09 20:53 ` Maxime Devos
2022-06-09 20:55 ` Maxime Devos
2022-06-09 21:03 ` Maxime Devos
2022-11-16 23:23 ` Mekeor Melire
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=079ca956e4d7c6b71921ee34638de012ae0a0c5f.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=53414@debbugs.gnu.org \
--cc=attila@lendvai.name \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.