From: Catonano <catonano@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: npm (mitigation)
Date: Tue, 25 Jul 2017 08:37:58 +0200 [thread overview]
Message-ID: <CAJ98PDxLFWSZAROVb9+ubEXjGjUUHT7zQE62bE6wCW+T+mA4UA@mail.gmail.com> (raw)
In-Reply-To: <87r2x57sjy.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
2017-07-24 17:39 GMT+02:00 Ricardo Wurmus <rekado@elephly.net>:
>
> Catonano <catonano@gmail.com> writes:
>
> >> 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 ?
>
> Jelle is referring to the work by Sander van der Burg, who presented
> “Deploying NPM packages with the Nix package manager” at FOSDEM 2017.
>
> Here’s the video:
>
> https://video.fosdem.org/2017/K.4.601/deploying_npm_
> packages_with_nix.vp8.webm
>
>
Yes, thanks to the both of you
Also his blog posts are enlightening but I must confess that I'm not sure I
can wrap my mind around the issue
It's larger and more nuanced than it looks like
I'll read some more about it in the next days
Thanks Jelle for the pointers
[-- Attachment #2: Type: text/html, Size: 1758 bytes --]
next prev parent reply other threads:[~2017-07-25 6:38 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
2017-07-24 15:39 ` Ricardo Wurmus
2017-07-25 6:37 ` Catonano [this message]
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=CAJ98PDxLFWSZAROVb9+ubEXjGjUUHT7zQE62bE6wCW+T+mA4UA@mail.gmail.com \
--to=catonano@gmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).