From: mvf <mvf@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] neovim-qt: update to 0.2.19, adopt
Date: Fri, 31 Jan 2025 07:54:26 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-54156@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]
There is a new pull request by mvf against master on the void-packages repository
https://github.com/mvf/void-packages pr/neovim-qt
https://github.com/void-linux/void-packages/pull/54156
neovim-qt: update to 0.2.19, adopt
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES** (been using it for days)
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/54156.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pr/neovim-qt-54156.patch --]
[-- Type: text/x-diff, Size: 1309 bytes --]
From 7e1794ec2ec7f569d88a2b36d44f4b74d17626e8 Mon Sep 17 00:00:00 2001
From: Matthias von Faber <mvf@gmx.eu>
Date: Thu, 30 Jan 2025 10:26:42 +0100
Subject: [PATCH] neovim-qt: update to 0.2.19, adopt
---
srcpkgs/neovim-qt/template | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/neovim-qt/template b/srcpkgs/neovim-qt/template
index b036245e96fe2e..088ec567d05406 100644
--- a/srcpkgs/neovim-qt/template
+++ b/srcpkgs/neovim-qt/template
@@ -1,18 +1,18 @@
# Template file for 'neovim-qt'
pkgname=neovim-qt
-version=0.2.18
-revision=2
+version=0.2.19
+revision=1
build_style=cmake
configure_args="-DENABLE_TESTS=OFF -DUSE_SYSTEM_MSGPACK=ON"
hostmakedepends="qt5-host-tools qt5-qmake neovim"
makedepends="msgpack-devel qt5-devel qt5-svg-devel"
-depends="neovim"
+depends="neovim qt5-svg"
short_desc="Neovim client library and GUI, in Qt5"
-maintainer="Orphaned <orphan@voidlinux.org>"
+maintainer="Matthias von Faber <mvf@gmx.eu>"
license="ISC"
homepage="https://github.com/equalsraf/neovim-qt"
distfiles="https://github.com/equalsraf/neovim-qt/archive/v${version}.tar.gz"
-checksum=b1e1e019946ecb106b3aea8e35fc6e367d2efce44ca1c1599a2ccdfb35a28635
+checksum=2c5a5de6813566aeec9449be61e1a8cd8ef85979a9e234d420f2882efcfde382
post_install() {
vlicense LICENSE
next reply other threads:[~2025-01-31 6:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 6:54 mvf [this message]
2025-02-02 23:05 ` sgn
2025-02-03 10:00 ` [PR PATCH] [Updated] " mvf
2025-02-03 10:01 ` neovim-qt: update to 0.2.19, switch to qt6, adopt mvf
2025-02-07 2:15 ` [PR PATCH] [Merged]: " classabbyamp
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-54156@inbox.vuxu.org \
--to=mvf@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).