From: Andy Wingo <wingo@igalia.com>
To: Jelle Licht <jlicht@fsfe.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [GSoC update] Npm & guix
Date: Mon, 25 Jul 2016 10:41:35 +0200 [thread overview]
Message-ID: <87zip6154w.fsf@igalia.com> (raw)
In-Reply-To: <CAPsKtfKcgA3DNk15xE6mQ1Pn3y4eRfgj29uVOF70S9m23ScYZQ@mail.gmail.com> (Jelle Licht's message of "Sun, 24 Jul 2016 03:06:52 +0200")
On Sun 24 Jul 2016 03:06, Jelle Licht <jlicht@fsfe.org> writes:
> On Ludo's advice, I snarfed Ricardo's recursive importer and bolted it
> on my npm importer. After leaving the importer running for a quite
> some hours (and making it more robust in the face of inconsistent npm
> information), it turns out that jQuery has a direct or indirect
> dependcy on about everything. We are talking pretty much all of the
> build systems, all of the testing frameworks and all of the test
> runners. Literally thousands of packages, and multiple (conflicting)
> versions of most.
Wow, how frustrating!
> This makes it IMHO a worthwhile goal bootstrap to a working test
> framework, with of course at first tests disabled for the dependencies
> of this test framework. Test frameworks all have an (indirect)
> dependency on the Coffeescript compiler, of which the first version
> was written in Ruby. Using this initial (alpha) compiler, and the
> awesome git-bisect command, I was able to subsequently compile and use
> the more modern (but still old) Coffeescript-in-coffeescript
> compilers.
For what it's worth, to me as a bystander this looks like great progress
:)
Andy
next prev parent reply other threads:[~2016-07-25 8:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-24 1:06 [GSoC update] Npm & guix Jelle Licht
2016-07-25 8:41 ` Andy Wingo [this message]
2016-07-25 11:33 ` Jan Nieuwenhuizen
2016-07-25 21:26 ` Ludovic Courtès
2016-07-29 14:53 ` Catonano
2016-07-29 15:26 ` Jelle Licht
2016-07-30 22:19 ` Package graph queries Ludovic Courtès
2016-08-11 4:37 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zip6154w.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=guix-devel@gnu.org \
--cc=jlicht@fsfe.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.