From: Catonano <catonano@gmail.com>
To: Jelle Licht <jlicht@fsfe.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: npm (mitigation)
Date: Mon, 17 Jul 2017 11:28:20 +0200 [thread overview]
Message-ID: <CAJ98PDxKVbknPPyfObo-_meYyUFUVFADvk1LmxjEwbbJKS6BWQ@mail.gmail.com> (raw)
In-Reply-To: <CAPsKtfKrcMa0RdB3EYJ6R8iUh7boKbH_59FUwtmspjBT_tUvaw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
2017-07-14 13:57 GMT+02:00 Jelle Licht <jlicht@fsfe.org>:
> Hi Catonano,
>
> I would be be happy to help you with this, but tbh, I am not comfortable
> discussing this in-depth on guix-devel, as this seems antithetical to Guix'
> goals.
>
Ok, at least we made this clear.
I'll keep the list off the hook, should I need to discuss tis further, in
the future.
Just for the record, I don't mean to conter thhe Guix aim. I consider this
as a temporary mitigation. Were "temporary" is the key word
Regardless, the biggest issue that remains is still that npm-land is mired
> in cyclical dependencies and a fun-but-not-actually unique dependency
> resolving scheme.
> I am currently working on a guile version of what Sander did for Nix for
> importing entire npm dependency trees, but this will likely lead to lots of
> programmatically
> defined packages instead of the guix approach of mostly-manually defining
> each package.
>
What ? Who is Sander ans what did the do for Nix ?
How is importing "entire npm dependencies trees" different than importing
one package at a time and building the dependency tree gradually ?
I have no problem with programmatically defined pacages, anyway ;-)
[-- Attachment #2: Type: text/html, Size: 1905 bytes --]
next prev parent reply other threads:[~2017-07-17 9:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 8:52 npm (mitigation) Catonano
2017-07-14 11:57 ` Jelle Licht
2017-07-15 3:34 ` Mike Gerwitz
2017-07-15 3:57 ` Jelle Licht
2017-07-15 17:39 ` Adonay Felipe Nogueira
2017-07-15 16:51 ` Adonay Felipe Nogueira
2017-07-17 9:45 ` Catonano
2017-07-18 2:12 ` Mike Gerwitz
2017-07-17 9:28 ` Catonano [this message]
2017-07-24 15:39 ` Ricardo Wurmus
2017-07-25 6:37 ` Catonano
2017-07-14 17:11 ` Jan Nieuwenhuizen
2017-07-17 9:32 ` Catonano
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=CAJ98PDxKVbknPPyfObo-_meYyUFUVFADvk1LmxjEwbbJKS6BWQ@mail.gmail.com \
--to=catonano@gmail.com \
--cc=guix-devel@gnu.org \
--cc=jlicht@fsfe.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 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).