all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Dave Thompson <davet@fsf.org>
Cc: guix-devel@gnu.org
Subject: Re: Packaging JavaScript libraries
Date: Wed, 03 Sep 2014 21:35:54 +0200	[thread overview]
Message-ID: <87d2bcfqed.fsf@gnu.org> (raw)
In-Reply-To: <8dzjegk1gs.fsf@freestation00.office.fsf.org> (Dave Thompson's message of "Wed, 03 Sep 2014 14:23:15 -0400")

Dave Thompson <davet@fsf.org> skribis:

> JavaScript source files are typically bundled in a web applications
> source tree or bundled by a JavaScript only package manager such as
> Bower.  Would it make sense to package JavaScript libraries in Guix?
> I'm not sure how to approach the packaging of JavaScript at the system
> level.

I think there are two cases:

  1. Web browser JavaScript libraries;
  2. Node.js (and similar) JavaScript libraries.

Packaging #2 seems useful to me, and since there’s already a widespread
packaging format for that (npm), it should be easy to convert them
automatically, like someone did for Nix.  For users the benefit is (1)
that there’s no need to switch to a different package manager, (2) you
get all the cool features of Guix, and (3) non-JS dependencies are also
handled (npm can compiled C++ extensions, but it relies on having a
working C++ environment at hand.)

I’ve just discovered Bower.  My guess is that there would be less
incentive to use Guix for #1, because it’s a tool targeting specifically
Web developers.

My 2¢,
Ludo’.

      parent reply	other threads:[~2014-09-03 19:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-03 18:23 Packaging JavaScript libraries Dave Thompson
2014-09-03 19:22 ` Thompson, David
2014-09-03 19:35 ` Ludovic Courtès [this message]

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=87d2bcfqed.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=davet@fsf.org \
    --cc=guix-devel@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.