all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: pinoaffe <pinoaffe@airmail.cc>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org,
	Katherine Cox-Buday <cox.katherine.e@gmail.com>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: Re: Merging the “binary” NPM importer?
Date: Mon, 11 Oct 2021 19:12:32 +0200	[thread overview]
Message-ID: <87ily3lc3j.fsf@airmail.cc> (raw)
In-Reply-To: <CAJ3okZ1aFcU_1ak+N2XbLTHcJS4YYca2wu+wkZVA4aOV+CB=og@mail.gmail.com>

Hi,

zimoun writes:
> Instead of a strong inclusion, one could imagine this importer as a
> regular package using GUIX_EXTENSION_PATH.  For instance, it could be:
>
>    guix install guix-import-npm
>
> then something like:
>
>   guix import-npm <options>
>
> This just works, modulo some polishing and doc. :-)  For an example,
> see the package gwl.  An example using another strategy is using a
> channel, for instance
> <https://framagit.org/tyreunom/guix-home-manager>.
>
> I have not checked if this "extension" system could work for
> subcommands as the importers, i.e., having something like:
>
>    guix import npm
>
> where this 'npm' would not be part of Guix proper (not in
> guix/import/) but instead would be a package extending Guix.

This would currently not work, but I've submitted a patch that would
make it work (with some performance concerns), and I think it should be
possible to resolve or at least significantly lessen those concerns.

However, I think inclusion in guix proper would encourage usage and make
maintenance easier (since maintaining two tightly coupled but separate
codebases is more work than maintaining a single codebase with the same
functionality)

While I would not be opposed to a package- or channel-based approach
(I initially set out to make a guix-npm-binary channel afterall),
merging it into guix-proper would definitely have my preference.

Kind regards,
pinoaffe


  reply	other threads:[~2021-10-11 17:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-19 13:01 Adding extra package importers pinoaffe
2021-09-19 14:44 ` Maxime Devos
2021-09-23 20:28 ` Merging the “binary” NPM importer? Ludovic Courtès
2021-09-23 23:13   ` pinoaffe
2021-09-26 13:37     ` Jelle Licht
2021-09-26 21:34       ` pinoaffe
2021-09-26 22:32         ` Philip McGrath
2021-09-27  8:57           ` pinoaffe
2021-09-27 15:13             ` Katherine Cox-Buday
2021-09-28 12:37       ` Ludovic Courtès
2021-09-25  3:17   ` Christine Lemmer-Webber
2021-10-08  1:51     ` Maxim Cournoyer
2021-10-08 14:16       ` Katherine Cox-Buday
2021-10-11 10:13         ` zimoun
2021-10-11 17:12           ` pinoaffe [this message]
2021-10-12 18:21       ` Timothy Sample
2021-10-14  1:26         ` Maxim Cournoyer
2021-10-14 13:58           ` Ludovic Courtès
2021-10-14 14:54             ` Opining on "modern" development practices (was Re: Merging the “binary” NPM importer?) Katherine Cox-Buday
2021-10-21 19:39               ` Ludovic Courtès
2021-10-28 15:01                 ` Katherine Cox-Buday
2021-10-29 12:33                   ` Ludovic Courtès
2021-10-29 14:54                     ` Katherine Cox-Buday

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=87ily3lc3j.fsf@airmail.cc \
    --to=pinoaffe@airmail.cc \
    --cc=cox.katherine.e@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=zimon.toutoune@gmail.com \
    /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.