From: unrealjo <unrealjo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: nodejs : update to 18.14.2
Date: Wed, 01 Mar 2023 20:07:24 +0100 [thread overview]
Message-ID: <20230301190724.czXgw65U2dyMq1ATe-tBfc6eZO2y-l2Io_DU0anPIUI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42525@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
New comment by unrealjo on void-packages repository
https://github.com/void-linux/void-packages/pull/42525#issuecomment-1450709381
Comment:
> How did you get the list of blockers? Almost all of them should work with nodejs 18 .
I thought that updating the nodejs-lts to 16.19.1 and switching dependencies from nodejs to nodejs-lts , will save me from the hassle of testing every program depending on nodejs .
So that we can focus on the update of nodejs to 18.14.2
> I am not sure what you mean, how failed?
In case switching dependencies of packages above (blockers) to nodejs-lts breaks some packages , we can at least make sure that **hostmakedepends** set to "nodejs-bin" instead of rebuilding (nodejs or nodejs-lts) which takes time to do .
<hr>
@paper42 , Aside from that, how about adding new packages (node.js-bin) so we will be able to use the latest stable version of node without breaking other packages, and I would like to maintain it as well.
next prev parent reply other threads:[~2023-03-01 19:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 14:40 [PR PATCH] " unrealjo
2023-03-01 14:43 ` [PR PATCH] [Updated] " unrealjo
2023-03-01 14:57 ` unrealjo
2023-03-01 15:04 ` unrealjo
2023-03-01 16:10 ` paper42
2023-03-01 19:07 ` unrealjo [this message]
2023-03-01 19:35 ` paper42
2023-03-01 19:36 ` paper42
2023-03-27 19:52 ` [PR PATCH] [Updated] " unrealjo
2023-03-28 12:36 ` [PR PATCH] [Closed]: " unrealjo
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=20230301190724.czXgw65U2dyMq1ATe-tBfc6eZO2y-l2Io_DU0anPIUI@z \
--to=unrealjo@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).