From: atweiden <atweiden@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] neovim: remove alternatives.
Date: Thu, 17 Mar 2022 02:05:37 +0100 [thread overview]
Message-ID: <20220317010537.A0o3WOkhIem5t36cJl8Lx4-FlMh--nxrESSOk43H-ag@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36165@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 404 bytes --]
There is an updated pull request by atweiden against master on the void-packages repository
https://github.com/atweiden/void-packages neovim
https://github.com/void-linux/void-packages/pull/36165
neovim: remove alternatives.
Closes #36164
#### Testing the changes
- I tested the changes in this PR: **YES**
A patch file from https://github.com/void-linux/void-packages/pull/36165.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-neovim-36165.patch --]
[-- Type: text/x-diff, Size: 1046 bytes --]
From 3fd93c3d4080d2bfe7f0ed15757233fe6beeef13 Mon Sep 17 00:00:00 2001
From: Andy Weidenbaum <atweiden@ioiojo.com>
Date: Wed, 16 Mar 2022 09:03:57 +1100
Subject: [PATCH] neovim: remove alternatives.
closes #36164
---
srcpkgs/neovim/template | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/srcpkgs/neovim/template b/srcpkgs/neovim/template
index 28cbc7e363cb..8137a88f9ef8 100644
--- a/srcpkgs/neovim/template
+++ b/srcpkgs/neovim/template
@@ -1,7 +1,7 @@
# Template file for 'neovim'
pkgname=neovim
version=0.6.1
-revision=1
+revision=2
build_style=cmake
build_helper="qemu"
configure_args="-DCMAKE_BUILD_TYPE=Release"
@@ -18,11 +18,7 @@ checksum=dd882c21a52e5999f656cae3f336b5fc702d52addd4d9b5cd3dc39cfff35e864
alternatives="
vi:vi:/usr/bin/nvim
- vi:vi.1:/usr/share/man/man1/nvim.1
- vi:view:/usr/bin/nvim
- vi:view.1:/usr/share/man/man1/nvim.1
- vim:vim:/usr/bin/nvim
- vim:vim.1:/usr/share/man/man1/nvim.1"
+ vi:vi.1:/usr/share/man/man1/nvim.1"
pre_configure() {
vsed -i runtime/CMakeLists.txt \
next prev parent reply other threads:[~2022-03-17 1:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 22:15 [PR PATCH] " atweiden
2022-03-16 5:44 ` atweiden
2022-03-16 6:29 ` Duncaen
2022-03-16 6:33 ` Duncaen
2022-03-16 6:34 ` Duncaen
2022-03-16 8:50 ` atweiden
2022-03-16 9:19 ` paper42
2022-03-17 1:05 ` atweiden [this message]
2022-03-17 1:07 ` atweiden
2022-03-17 1:07 ` atweiden
2022-03-17 1:11 ` [PR PATCH] [Closed]: " Duncaen
2022-03-27 18:28 ` [RFC] " Vaelatern
2022-03-27 20:35 ` paper42
2022-03-27 20:35 ` [PR PATCH] [Closed]: " paper42
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=20220317010537.A0o3WOkhIem5t36cJl8Lx4-FlMh--nxrESSOk43H-ag@z \
--to=atweiden@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).