From: thatboyjake <thatboyjake@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] neovim: update to 0.7.0.
Date: Sat, 23 Apr 2022 04:44:43 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36823@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 478 bytes --]
There is a new pull request by thatboyjake against master on the void-packages repository
https://github.com/thatboyjake/void-packages master
https://github.com/void-linux/void-packages/pull/36823
neovim: update to 0.7.0.
#### Testing the changes
- I tested the changes in this PR: YES
#### Local build testing
- I built this PR locally for my native architecture, (x86_x64-musl)
A patch file from https://github.com/void-linux/void-packages/pull/36823.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-36823.patch --]
[-- Type: text/x-diff, Size: 1150 bytes --]
From 358ec1e3d7a8e8a2163466ab423d64912ca262f1 Mon Sep 17 00:00:00 2001
From: thatboyjake <jakerhackl@gmail.com>
Date: Fri, 22 Apr 2022 16:39:17 -0500
Subject: [PATCH] neovim: update to 0.7.0.
---
srcpkgs/neovim/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/neovim/template b/srcpkgs/neovim/template
index 28cbc7e363cb..42cecfb6cf6c 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
+version=0.7.0
+revision=0
build_style=cmake
build_helper="qemu"
configure_args="-DCMAKE_BUILD_TYPE=Release"
@@ -14,7 +14,7 @@ maintainer="Steve Prybylski <sa.prybylx@gmail.com>"
license="Apache-2.0, custom:Vim"
homepage="https://neovim.io"
distfiles="https://github.com/neovim/neovim/archive/v${version}.tar.gz"
-checksum=dd882c21a52e5999f656cae3f336b5fc702d52addd4d9b5cd3dc39cfff35e864
+checksum=792a9c55d5d5f4a5148d475847267df309d65fb20f05523f21c1319ea8a6c7df
alternatives="
vi:vi:/usr/bin/nvim
@@ -30,5 +30,5 @@ pre_configure() {
}
post_install() {
- vlicense LICENSE
+ vlicense LICENSE.txt
}
next reply other threads:[~2022-04-23 2:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 2:44 thatboyjake [this message]
2022-04-23 2:49 ` classabbyamp
2022-04-23 3:12 ` thatboyjake
2022-04-23 3:13 ` [PR PATCH] [Closed]: " thatboyjake
-- strict thread matches above, loose matches on Subject: below --
2022-04-21 15:44 [PR PATCH] " siduck
2022-04-15 12:48 kartikynwa
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36823@inbox.vuxu.org \
--to=thatboyjake@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).