unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Yuan Fu <casouri@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Hosting tree-sitter pre-built language definitions on ELPA?
Date: Tue, 11 Oct 2022 16:51:59 -0400	[thread overview]
Message-ID: <jwvfsfurt0x.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <6AC1140D-C4BA-4A39-9474-F127CF79DF28@gmail.com> (Yuan Fu's message of "Sat, 1 Oct 2022 21:47:11 -0700")

Yuan Fu [2022-10-01 21:47:11] wrote:
> I wonder if we can host pre-built language definitions for languages we
> provide tree-sitter support OOTB on ELPA, so users can easily download them?

[ Coming late to this discussion, sorry.  ]

We could consider it, but as Eli mentioned, it's not clear what we'll
need, so I think it's best to wait.  FWIW, there are similar questions
for Emacs modules distributed via (Non)GNU ELPA (such as the `libpq`
module), and currently we just don't do it.

Note also that the native ELisp compiler brings GCC as a dependency of
Emacs, so if that becomes the norm, we might prefer to just build the
language definition locally from its C version (which is not actually
its source), and maybe we'll want to host *those* i.e. the pre-digested
language definitions in their C form.

Hosting them on a gnu.org machine would make it easier to make their
installation (semi)automatic since we usually don't like to download
random code directly from third parties with which we have no
shared agreement.  But if the language definitions can be installed as
Debian packages, it might not be necessary at all.


        Stefan




  parent reply	other threads:[~2022-10-11 20:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-02  4:47 Hosting tree-sitter pre-built language definitions on ELPA? Yuan Fu
2022-10-02  5:15 ` Po Lu
2022-10-02  5:57   ` Yuan Fu
2022-10-02  6:19   ` Eli Zaretskii
2022-10-02 13:37     ` chad
2022-10-02 13:52       ` Eli Zaretskii
2022-10-02 16:36         ` chad
2022-10-02 17:06           ` Eli Zaretskii
2022-10-02 22:17             ` Yuan Fu
2022-10-03 15:56               ` Eli Zaretskii
2022-10-04 16:31                 ` Yuan Fu
2022-10-03  0:45             ` chad
2022-10-12 10:54         ` Stephen Leake
2022-10-12 13:08           ` Eli Zaretskii
2022-10-02  6:17 ` Eli Zaretskii
2022-10-11 20:51 ` Stefan Monnier [this message]
2022-10-12  7:00   ` Yuan Fu

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvfsfurt0x.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=casouri@gmail.com \
    --cc=emacs-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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).