From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: vim: add options for different build variants.
Date: Fri, 16 Jul 2021 21:15:32 +0200 [thread overview]
Message-ID: <20210716191532.6vIPzrRRo6JCCr8zRj_NZDd_FYXh07Di_64EEK21I74@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31871@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 707 bytes --]
There's a merged pull request on the void-packages repository
vim: add options for different build variants.
https://github.com/void-linux/void-packages/pull/31871
Description:
Our vim build support different configurations, but the template builds all of them by default. This is a problem if one just wants a "small" vim as the dependency chain is huge (featuring LLVM, MozJS, Rust, ...).
Add three options to configure the builds:
- x11 enables the X11-clipboard build
- gtk3 enables gvim
- huge enables language interpreters (disabled for cross)
Should have no functional difference, maintenance overhead is neglegible.
I cleaned up some flags that got removed in 2019.
cc @NeelChotai
prev parent reply other threads:[~2021-07-16 19:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 14:23 [PR PATCH] " leahneukirchen
2021-07-09 14:24 ` [PR PATCH] [Updated] " leahneukirchen
2021-07-09 14:29 ` ericonr
2021-07-09 14:45 ` leahneukirchen
2021-07-09 15:43 ` [PR PATCH] [Updated] " leahneukirchen
2021-07-09 15:43 ` [PR PATCH] [Closed]: " leahneukirchen
2021-07-09 15:45 ` [PR PATCH] [Updated] " leahneukirchen
2021-07-09 15:46 ` leahneukirchen
2021-07-09 20:43 ` Piraty
2021-07-16 19:15 ` leahneukirchen [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=20210716191532.6vIPzrRRo6JCCr8zRj_NZDd_FYXh07Di_64EEK21I74@z \
--to=leahneukirchen@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).