unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Ryan Prior <rprior@protonmail.com>, jgart <jgart@dismail.de>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: developing javascript with guix
Date: Sat, 30 Jul 2022 21:44:07 +0200	[thread overview]
Message-ID: <3dfa37a6-2be6-5edd-596d-451c1c829796@telenet.be> (raw)
In-Reply-To: <7K0vjV4NvEKb0D-wEmmFrZrnJIJRCzAAPhxOe0b4qRqr10cYam8bO2M2mgiQcBD5tO08B7NqFBo_xn-LCDzg-sS_VKdzVhm4_cwpceZyi60=@protonmail.com>


[-- Attachment #1.1.1.1: Type: text/plain, Size: 920 bytes --]


On 28-07-2022 01:15, Ryan Prior wrote:
> Why isn't node a dependency for node-mersenne though?

It is. node-mersenne uses node-build-system, which has node (or 
node-lts, dunno) in its implicit inputs.

Did you mean: 'Why isn't node propagated?'

For the same reasons as why any plugins don't propagate the thing they 
are plugging in, and why any library doesn't propagate its interpreter:

  * There is more than one implementation, how would Guix know which one
    you'd like?
  * Propagation stops you from separately updating the library and the
    interpreter (with "guix package -u this-package", or time machines,
    or defining a package variant).  (Actually, "guix package -u
    this-package" will ‘succeed’ because collision detection is disabled
    IIUC, but you can't decide which one wins)
  * ???

Also, see my answer on 'Is there really a use case for shipping ...’.


[-- Attachment #1.1.1.2: Type: text/html, Size: 1492 bytes --]

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  parent reply	other threads:[~2022-07-30 20:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27  0:25 developing javascript with guix jgart
2022-07-27  9:33 ` Maxime Devos
2022-07-27 22:25   ` jgart
2022-07-27 23:15     ` Ryan Prior
2022-07-30 13:40       ` Luis Felipe
2022-07-30 16:04         ` bokr
2022-08-03 14:26         ` david larsson
2022-07-30 19:36       ` Maxime Devos
2022-07-30 19:44       ` Maxime Devos [this message]
2022-07-30 19:50       ` Maxime Devos
2022-07-30 20:22       ` Maxime Devos
2022-08-03 13:18       ` Giovanni Biscuolo
2022-07-30 19:35     ` Maxime Devos

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3dfa37a6-2be6-5edd-596d-451c1c829796@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=guix-devel@gnu.org \
    --cc=jgart@dismail.de \
    --cc=rprior@protonmail.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).