[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: On merging the npm importer
From: |
Ludovic Courtès |
Subject: |
Re: On merging the npm importer |
Date: |
Thu, 30 Mar 2017 16:50:52 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Hello!
Christopher Allan Webber <address@hidden> skribis:
> Jan Nieuwenhuizen writes:
[...]
>> We have a working importer for npm packages written by Jelle that I have
>> been using for about half a year. It can use some improvements and
>> that's why I think we should merge it.
>>
>> Have alook at my npm branch here, rebased on master
>>
>> https://gitlab.com/janneke/guix
>
> Would like to review soon, though I'll say that I think unless there are
> serious problems, we should probably merge it. Avoiding bitrot is prety
> important, and at the very least I don't think it will hurt to have it
> merged.
Agreed. If there are tests and doc and it’s all “reasonable”, which I
think it is, I second that!
>> I suggest to not add any npm package to Guix that is the result of using
>> the --binary option and to build a base of full-source/sanitized npm
>> packages.
>
> Cool... makes sense to me to have this as something we don't use for
> Guix packages, but which might make Guix more useful for people who have
> to use npm in the awkward "real world" that is the current state of npm.
How terrible must it be to live in the “real world”! :-)
Ludo’.