From: Efraim Flashner <efraim@flashner.co.il>
To: goodoldpaul@autistici.org
Cc: julien@lepiller.eu, 36599@debbugs.gnu.org
Subject: [bug#36599] [PATCH] gnu: Add node-semver. (Updated)
Date: Fri, 17 Apr 2020 18:03:52 +0300 [thread overview]
Message-ID: <20200417150352.GB9867@E5400> (raw)
In-Reply-To: <0dc7cf533fa5aa29a12e7b1da9532869@autistici.org>
[-- Attachment #1: Type: text/plain, Size: 2384 bytes --]
On Fri, Apr 17, 2020 at 02:54:43PM +0000, goodoldpaul@autistici.org wrote:
> Hi Julien,
>
> > Does npm install the test.js files when run by ittself (in which case we
> > replicate its behavior), or does it have a mechanism to know what files
> > to install? If so we thould replicate that mecanism.
>
> On my system I get
>
> giacomo@frarch /tmp$ npm i semver
> npm WARN saveError ENOENT: no such file or directory, open
> '/tmp/package.json'
> npm WARN enoent ENOENT: no such file or directory, open '/tmp/package.json'
> npm WARN tmp No description
> npm WARN tmp No repository field.
> npm WARN tmp No README data
> npm WARN tmp No license field.
>
> + semver@7.3.2
> added 1 package and audited 1 package in 0.626s
> found 0 vulnerabilities
>
> giacomo@frarch /tmp$ ls -l node_modules/semver/
> total 48
> drwxr-xr-x 2 giacomo giacomo 60 Apr 17 16:43 bin/
> -rw-r--r-- 1 giacomo giacomo 2257 Oct 26 1985 CHANGELOG.md
> drwxr-xr-x 2 giacomo giacomo 120 Apr 17 16:43 classes/
> drwxr-xr-x 2 giacomo giacomo 520 Apr 17 16:43 functions/
> -rw-r--r-- 1 giacomo giacomo 1982 Oct 26 1985 index.js
> drwxr-xr-x 2 giacomo giacomo 120 Apr 17 16:43 internal/
> -rw-r--r-- 1 giacomo giacomo 765 Oct 26 1985 LICENSE
> -rw-r--r-- 1 giacomo giacomo 1645 Apr 17 16:43 package.json
> -rw-r--r-- 1 giacomo giacomo 69 Oct 26 1985 preload.js
> -rw-r--r-- 1 giacomo giacomo 619 Oct 26 1985 range.bnf
> drwxr-xr-x 2 giacomo giacomo 260 Apr 17 16:43 ranges/
> -rw-r--r-- 1 giacomo giacomo 22109 Oct 26 1985 README.md
>
> so I believe that npm uses the "files" key [0] in package.json to decide
> what to install.
>
Thanks for looking into it.
> I'm definitely available to implement that but it could take a week or two,
> if we feel it should be changed right away I'm probably not the best person
> to do that.
>
> What do you think? Should I open another issue about this?
I think we should fix it, but it shouldn't block getting your package
into Guix. Go ahead and open a new issue for it.
>
> Giacomo
>
> [0]: https://github.com/npm/node-semver/blob/master/package.json#L21
>
>
>
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-04-17 15:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 12:12 [bug#36599] [PATCH] gnu: Add node-semver Giacomo Leidi
2019-09-02 12:49 ` Ludovic Courtès
2019-09-02 14:50 ` Julien Lepiller
2019-09-02 17:13 ` goodoldpaul
2020-04-07 23:06 ` [bug#36599] [PATCH] gnu: Add node-semver. (Updated) goodoldpaul
2020-04-09 20:01 ` Efraim Flashner
2020-04-15 15:36 ` goodoldpaul
2020-04-15 17:09 ` Julien Lepiller
2020-04-18 18:39 ` bug#36599: " Efraim Flashner
2020-04-17 14:54 ` [bug#36599] " goodoldpaul
2020-04-17 15:03 ` Efraim Flashner [this message]
2020-04-17 16:09 ` Julien Lepiller
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=20200417150352.GB9867@E5400 \
--to=efraim@flashner.co.il \
--cc=36599@debbugs.gnu.org \
--cc=goodoldpaul@autistici.org \
--cc=julien@lepiller.eu \
/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).