From: gbrlsnchs <gbrlsnchs@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: tree-sitter: build and install tree-sitter CLI.
Date: Mon, 08 Mar 2021 18:50:36 +0100 [thread overview]
Message-ID: <20210308175036.ftlTZ1HYYga-UBxrkD_s-bAWGAXxZ6kYLeu7Z3X750Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29272@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
New comment by gbrlsnchs on void-packages repository
https://github.com/void-linux/void-packages/pull/29272#issuecomment-792947486
Comment:
> I'm still somewhat pending towards shipping the CLI in devel, since packages like neovim will come to depend on it and it's more stuff to pull in (probably much bigger than the library) that most people won't be using. If you want to generate grammars, you can grab the -devel package.
Neovim 0.5 only uses `tree-sitter-devel` as a `makedepends` dependency (example [here](https://github.com/gbrlsnchs/void-packages/blob/8030a6713946c4dedd2c89fbaf25988099e1a029/srcpkgs/neovim/template) from my custom packaging), so its end-users won't necessarily install `tree-sitter-devel` on their machines in order to run Neovim, since only `tree-sitter` (which includes `libtree-sitter`, needed by Neovim) is needed.
That's why I think shipping `libtree-sitter` and the CLI together in the same package is a better idea, and I think it's a lot more expected than having the CLI in a `-devel` package.
next prev parent reply other threads:[~2021-03-08 17:50 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 17:58 [PR PATCH] " gbrlsnchs
2021-03-07 21:33 ` ericonr
2021-03-07 21:38 ` ericonr
2021-03-08 0:06 ` gbrlsnchs
2021-03-08 0:34 ` ericonr
2021-03-08 0:45 ` gbrlsnchs
2021-03-08 2:27 ` ericonr
2021-03-08 14:26 ` gbrlsnchs
2021-03-08 14:27 ` gbrlsnchs
2021-03-08 14:27 ` gbrlsnchs
2021-03-08 15:13 ` ericonr
2021-03-08 17:50 ` gbrlsnchs [this message]
2021-03-08 18:27 ` ericonr
2021-03-08 18:27 ` ericonr
2021-03-08 18:49 ` gbrlsnchs
2021-03-08 18:55 ` FollieHiyuki
2021-03-08 19:03 ` ericonr
2021-03-08 20:50 ` [PR PATCH] [Updated] " gbrlsnchs
2021-03-08 20:51 ` gbrlsnchs
2021-03-08 20:53 ` gbrlsnchs
2021-03-08 20:56 ` gbrlsnchs
2021-03-08 22:52 ` ericonr
2021-03-09 0:31 ` gbrlsnchs
2021-03-09 0:39 ` ericonr
2021-03-09 0:39 ` ericonr
2021-03-09 1:02 ` gbrlsnchs
2021-03-09 1:06 ` [PR PATCH] [Updated] " gbrlsnchs
2021-03-09 8:51 ` FollieHiyuki
2021-03-15 23:48 ` [PR PATCH] [Closed]: " ericonr
2021-03-15 23:48 ` ericonr
2021-03-15 23:55 ` gbrlsnchs
2021-03-16 0:10 ` ericonr
2021-03-16 0:11 ` ericonr
2021-03-16 13:40 ` gbrlsnchs
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=20210308175036.ftlTZ1HYYga-UBxrkD_s-bAWGAXxZ6kYLeu7Z3X750Q@z \
--to=gbrlsnchs@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).