From: Mark H Weaver <mhw@netris.org>
To: Pierre Langlois <pierre.langlois@gmx.com>
Cc: 43228@debbugs.gnu.org
Subject: bug#43228: r-v8 doesn't build since node 10.22 update
Date: Sun, 06 Sep 2020 15:42:27 -0400 [thread overview]
Message-ID: <878sdmr8sh.fsf@netris.org> (raw)
In-Reply-To: <87pn6z5f4j.fsf@gmx.com>
Hi Pierre,
Your new patch looks good to me, but the node-10.22 source field could
be simplified to avoid repeating the unchanged field (especially the
snippet), by inheriting from (package-source node) like this:
--8<---------------cut here---------------start------------->8---
(source (origin
(inherit (package-source node))
(uri (string-append "https://nodejs.org/dist/v" version
"/node-v" version ".tar.xz"))
(sha256
(base32
"1nz18fa550li10r0kzsm28c2rvvq61nq8bqdygip0rmvbi2paxg0"))))
--8<---------------cut here---------------end--------------->8---
Also, it would be great to find a way to fit in the subject line that
10.22 is also being kept as a separate binding, especially since "guix
build node" and most other user commands will still build 10.22. Maybe
something like this:
gnu: node: Downgrade to 10.20.0; add separate 'node-10.22' binding.
What do you think?
Anyway, feel free to push this, preferably after incorporating these
suggestions. If I'm not mistaken, the simplification suggested above
should not change the .drv file, and therefore not entail a rebuild, so
testing it should be very quick.
Thanks!
Mark
next prev parent reply other threads:[~2020-09-06 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 17:44 bug#43228: r-v8 doesn't build since node 10.22 update Pierre Langlois
2020-09-05 18:35 ` Mark H Weaver
2020-09-05 19:29 ` Pierre Langlois
2020-09-05 23:13 ` Mark H Weaver
2020-09-06 11:17 ` Pierre Langlois
2020-09-06 19:42 ` Mark H Weaver [this message]
2020-09-06 22:23 ` Pierre Langlois
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=878sdmr8sh.fsf@netris.org \
--to=mhw@netris.org \
--cc=43228@debbugs.gnu.org \
--cc=pierre.langlois@gmx.com \
/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.