all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jelle Licht <jlicht@fsfe.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: GSoC NPM
Date: Fri, 2 Sep 2016 17:33:06 +0200	[thread overview]
Message-ID: <CAPsKtfLY80iEU8NF_Xh4f0gKy=NiDnksLPgdPfTrU9vEW+OGCQ@mail.gmail.com> (raw)
In-Reply-To: <87shtiz8f7.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2023 bytes --]

Hi Jan,

Thanks for your interest and work. I am currently quite occupied with
getting ready
for my next year of studies, so I will only shortly address your points;

The short of it is that the dist tarball does not always contain the actual
source code.
Examples of this include generated code, minified code etc.

The devDependencies are, in these cases, the things we need to be able to
actually
build the package. Examples of this include gulp, grunt, and several
testing frameworks.

For simple packages, the difference between a npm tarball and a GH
tarball/repo are
non-existent. I made the choice to skip the npm tarball because I'd rather
err on the
side of caution, and not let people download and run these non-source
packages by accident ;-).

I will have more time to see this through next week.

- Jelle


2016-09-02 16:24 GMT+02:00 Jan Nieuwenhuizen <janneke@gnu.org>:

> Jelle Licht writes:
>
> Hi Jelle!
>
> > - The ability to parse npm version data
> > - An npm backend for ~guix import~
> > - Npm modules in guix
> > - An actual build system for npm packages
>
> That's amazing.  I played with it today and noticed that it always
> downloads devDependencies.  Why is that...I disabled that because
> I think I don't need those?
>
> Also, I found that you prefer going through the repository/github
> instead of using the dist tarball.  Why is that?  Some packages do not
> have a repository field, such as `http'.  I changed that to prefer using
> the dist tarball and use repository as fallback.  You probably want to
> change that order?
>
> I made some other small changes, see attached patch, to be able to
> download all packages that I need, notably: cjson, http and xmldom.
>
> Thanks again for your amazing work, hoping to have this in master soon.
>
> Greetings,
> Jan
>
>
>
> --
> Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
> Freelance IT http://JoyofSource.com | Avatar®  http://AvatarAcademy.nl
>
>

[-- Attachment #2: Type: text/html, Size: 2838 bytes --]

  parent reply	other threads:[~2016-09-02 15:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23  9:07 GSoC NPM Jelle Licht
2016-08-25 10:24 ` Ricardo Wurmus
2016-08-27 13:12   ` Jelle Licht
2016-09-06 23:21     ` Catonano
2016-08-27 21:43 ` Ludovic Courtès
2016-09-06 20:00   ` Christopher Allan Webber
2016-09-02 14:24 ` Jan Nieuwenhuizen
2016-09-02 15:27   ` Thompson, David
2016-09-02 16:23     ` Jan Nieuwenhuizen
2016-09-02 15:33   ` Jelle Licht [this message]
2016-09-04 14:11     ` Jan Nieuwenhuizen
2016-09-06 15:48       ` Thompson, David
2016-09-06 16:50         ` NPM and trusted binaries Pjotr Prins
2016-09-07 12:25           ` Ludovic Courtès
2016-09-07 17:51             ` Jan Nieuwenhuizen
2016-09-08  7:01               ` Pjotr Prins
2016-09-08  8:29                 ` Jelle Licht
2016-09-08  2:45           ` Mike Gerwitz
2016-09-08  8:45             ` Jan Nieuwenhuizen
2016-09-08 17:31               ` Mike Gerwitz
2016-09-08 19:54                 ` Jan Nieuwenhuizen
2016-09-09  0:31                   ` Mike Gerwitz
2016-09-09  8:45                     ` Ludovic Courtès
2016-09-09  9:26                       ` Pjotr Prins

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='CAPsKtfLY80iEU8NF_Xh4f0gKy=NiDnksLPgdPfTrU9vEW+OGCQ@mail.gmail.com' \
    --to=jlicht@fsfe.org \
    --cc=guix-devel@gnu.org \
    --cc=janneke@gnu.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 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.