From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org,divoplade <d@divoplade.fr>
Subject: Re: Is there a NPM importer?
Date: Mon, 18 May 2020 16:21:37 -0400 [thread overview]
Message-ID: <9FA62817-5CEC-491F-9CFA-5DE0FF228834@lepiller.eu> (raw)
In-Reply-To: <ff1578f8c30e7043be2741d0a76fe856734c39cd.camel@divoplade.fr>
Le 18 mai 2020 15:00:26 GMT-04:00, divoplade <d@divoplade.fr> a écrit :
>Hello Guix users :)
>
>Browsing through the web, I found a few discussions about an NPM
>importer.
>
>Nov 2018: https://www.mail-archive.com/guix-devel@gnu.org/msg44700.html
>
>Mar 2017:
>https://lists.gnu.org/archive/html/guix-devel/2017-03/msg00814.html
>
>What is the status of this?
When considering build-time dependencies, there are many cycles that makes an importer almost impossible to create. There is some code that works (at least it used to work) when you don't need a recursive import, but it would be useless because most packages require thousands of packages at build time.
I haven't been working on this since quite some time, and I don't think I'm going to take that time soon. If anyone is interested, I still think we need to build a backtracking startegy in our importer infrastructure (we could have a constraint solver do the job, but we would need complete information about the npm repo. We can only look up package by package) and import a minimal path, taking version constraints into account. Basically, backtrack on loops.
next prev parent reply other threads:[~2020-05-18 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 19:00 Is there a NPM importer? divoplade
2020-05-18 20:21 ` Julien Lepiller [this message]
2020-05-18 20:48 ` divoplade
2020-05-18 21:00 ` Julien Lepiller
2020-05-19 7:12 ` divoplade
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=9FA62817-5CEC-491F-9CFA-5DE0FF228834@lepiller.eu \
--to=julien@lepiller.eu \
--cc=d@divoplade.fr \
--cc=help-guix@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.
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).