Github messages for voidlinux
 help / color / mirror / Atom feed
From: sweiglbosker <sweiglbosker@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: neovide-0.13.3
Date: Fri, 13 Dec 2024 22:27:28 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53515@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 784 bytes --]

There is a new pull request by sweiglbosker against master on the void-packages repository

https://github.com/sweiglbosker/void-packages neovide
https://github.com/void-linux/void-packages/pull/53515

New package: neovide-0.13.3
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**


#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**

#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)

**Addresses:** #43688 


A patch file from https://github.com/void-linux/void-packages/pull/53515.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-neovide-53515.patch --]
[-- Type: text/x-diff, Size: 1236 bytes --]

From ea537270256109d9425a12b767e53e858d21b948 Mon Sep 17 00:00:00 2001
From: Stefan Weigl-Bosker <stefan@s00.xyz>
Date: Fri, 13 Dec 2024 16:15:47 -0500
Subject: [PATCH] New package: neovide-0.13.3

---
 srcpkgs/neovide/template | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)
 create mode 100644 srcpkgs/neovide/template

diff --git a/srcpkgs/neovide/template b/srcpkgs/neovide/template
new file mode 100644
index 00000000000000..76e050666ca012
--- /dev/null
+++ b/srcpkgs/neovide/template
@@ -0,0 +1,19 @@
+# Template file for 'neovide'
+pkgname=neovide
+version=0.13.3
+revision=1
+build_style=cargo
+hostmakedepends="pkg-config python3 cmake curl"
+makedepends="fontconfig-devel freetype-devel libxcb-devel libX11-devel gtk+3-devel libglvnd-devel sndio-devel openssl-devel libcxx-devel"
+depends="neovim gtk+3"
+short_desc="No Nonsense Neovim Client in Rust"
+maintainer="Stefan Weigl-Bosker <stefan@s00.xyz>"
+license="MIT"
+homepage="neovide.dev"
+changelog="https://github.com/neovide/neovide/compare/0.13.2...0.13.3"
+distfiles="https://github.com/neovide/neovide/archive/refs/tags/${version}.tar.gz"
+checksum=21c8eaa53cf3290d2b1405c8cb2cde5f39bc14ef597b328e76f1789b0ef3539a
+
+post_install() {
+	vlicense LICENSE
+}

             reply	other threads:[~2024-12-13 21:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13 21:27 sweiglbosker [this message]
2024-12-14  4:04 ` [PR PATCH] [Updated] " sweiglbosker
2024-12-19 21:14 ` [PR REVIEW] " Bnyro
2024-12-19 21:17 ` Bnyro
2024-12-20 19:42 ` [PR PATCH] [Updated] " sweiglbosker
2024-12-20 19:44 ` sweiglbosker
2024-12-20 19:44 ` sweiglbosker
2024-12-20 22:18 ` Bnyro
2024-12-21  4:46 ` sweiglbosker
2025-01-01 18:37 ` [PR PATCH] [Updated] " sweiglbosker
2025-01-01 18:39 ` sweiglbosker
2025-01-01 18:40 ` sweiglbosker
  -- strict thread matches above, loose matches on Subject: below --
2024-08-02  6:08 [PR PATCH] " hesam-init

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-53515@inbox.vuxu.org \
    --to=sweiglbosker@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).