unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: jgart <jgart@dismail.de>, 62664@debbugs.gnu.org
Cc: Giovanni Biscuolo <g@xelera.eu>,
	Rostislav Svoboda <rostislav.svoboda@gmail.com>,
	Nicolas Goaziou <mail@nicolasgoaziou.fr>,
	Brian Cully <bjc@spork.org>
Subject: [bug#62664] [PATCH] [WIP] gnu: Add emacs-copilot.
Date: Mon, 23 Dec 2024 20:02:47 +0100	[thread overview]
Message-ID: <8c9674d7dc27f87e2a14bd665f46d1d95bedf556.camel@gmail.com> (raw)
In-Reply-To: <87o712gsey.fsf@dismail.de>

Am Montag, dem 23.12.2024 um 12:34 -0600 schrieb jgart:
> 
> Actually looking at this package more carefully, the reason it needs
> node is to npm install copilot-node-server which has an unclear
> license:
> 
> https://github.com/jfcherng/copilot-node-server
> 
> Here's what nixpkgs did:
> 
> https://github.com/NixOS/nixpkgs/blob/master/pkgs/by-name/co/copilot-node-server/package.nix#L38
> 
> Will this be a problem for emacs-copilot since we should include
> copilot-node-server as a required dependency instead of installing it
> via the npm wrapper?
> 
> If yes, I can close this issue and put this in a Guix channel
> instead.
Unbundling would be nicer, but if you don't need to download the
internet as part of the build or on first start to fetch all the
dependencies (i.e. if you can properly package it with available
sources + node), then you may forgo that for now.  That's a big if
however, one that rarely holds in JS ecosystems.

> Would be unfortunate though, since this is becoming a popular package
> in the Emacs ecosystem.
Selling your data to Microsoft should be less popular, then.

Cheers




  reply	other threads:[~2024-12-23 19:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04 14:30 [bug#62664] [PATCH] [WIP] gnu: Add emacs-copilot Rostislav Svoboda
2023-04-04 14:35 ` Rostislav Svoboda
2023-04-04 14:54 ` jgart via Guix-patches via
2023-04-04 19:19 ` Liliana Marie Prikler
2023-04-05 13:07   ` Giovanni Biscuolo
2023-04-06 19:34   ` Brian Cully via Guix-patches via
2023-04-07  5:00 ` [bug#62664] jgart via Guix-patches via
2024-10-17 22:26   ` [bug#62664] [PATCH] [WIP] gnu: Add emacs-copilot jgart via Guix-patches via
2024-10-27 10:39     ` Nicolas Goaziou via Guix-patches via
2024-10-28  2:41       ` jgart via Guix-patches via
2024-12-23 17:47         ` jgart via Guix-patches via
2024-12-23 18:34           ` jgart via Guix-patches via
2024-12-23 19:02             ` Liliana Marie Prikler [this message]
2024-10-28  2:40 ` [bug#62664] [PATCH v2] " jgart via Guix-patches via
2024-12-23 17:44 ` [bug#62664] [PATCH v3] " jgart via Guix-patches via
2024-12-24  8:20   ` Liliana Marie Prikler
2024-12-24 15:03     ` jgart via Guix-patches via
2024-12-24 15:13       ` jgart via Guix-patches via
2024-12-24 18:11       ` Liliana Marie Prikler

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=8c9674d7dc27f87e2a14bd665f46d1d95bedf556.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=62664@debbugs.gnu.org \
    --cc=bjc@spork.org \
    --cc=g@xelera.eu \
    --cc=jgart@dismail.de \
    --cc=mail@nicolasgoaziou.fr \
    --cc=rostislav.svoboda@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 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).