all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Attila Lendvai <attila@lendvai.name>
To: "53414@debbugs.gnu.org" <53414@debbugs.gnu.org>
Subject: [bug#53414] [PATCH] update Node LTS to 16.13.2
Date: Fri, 25 Feb 2022 13:09:11 +0000	[thread overview]
Message-ID: <sd9Oi7dJHu-Htzpw-2nTg6xUR2n84wErt6gEOc11sW5xV7e1PMvWS64IrH7SWDBBFqe8Xy8QLzvlSApQ2mzRdgPvaK6woyqnW9tNDS1Gvso=@lendvai.name> (raw)
In-Reply-To: <145389012.1197903.1642777885519@privateemail.com>

> 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.

note that this supersedes https://issues.guix.gnu.org/48396 (i don't know what
is the right way to record that fact in debbugs, besides this note).

--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“Everything is interesting if you go into it *deeply* enough.”
	— Richard Feynman (1918–1988)





  parent reply	other threads:[~2022-02-25 13:43 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 [this message]
2022-02-25 15:59   ` Maxime Devos
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='sd9Oi7dJHu-Htzpw-2nTg6xUR2n84wErt6gEOc11sW5xV7e1PMvWS64IrH7SWDBBFqe8Xy8QLzvlSApQ2mzRdgPvaK6woyqnW9tNDS1Gvso=@lendvai.name' \
    --to=attila@lendvai.name \
    --cc=53414@debbugs.gnu.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. 
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.