From: Goorzhel <Goorzhel@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: ncgopher-0.4.0
Date: Wed, 03 Aug 2022 03:07:04 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38444@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
There is a new pull request by Goorzhel against master on the void-packages repository
https://github.com/Goorzhel/void-packages ncgopher
https://github.com/void-linux/void-packages/pull/38444
New package: ncgopher-0.4.0
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**
<!-- 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/38444.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-ncgopher-38444.patch --]
[-- Type: text/x-diff, Size: 1081 bytes --]
From 9052a96eb15004f2a69d37b68f0f0db0e9dc2a72 Mon Sep 17 00:00:00 2001
From: Antonio Gurgel <antonio@goorzhel.com>
Date: Tue, 2 Aug 2022 17:58:27 -0700
Subject: [PATCH] New package: ncgopher-0.4.0
---
srcpkgs/ncgopher/template | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
create mode 100644 srcpkgs/ncgopher/template
diff --git a/srcpkgs/ncgopher/template b/srcpkgs/ncgopher/template
new file mode 100644
index 000000000000..098bb544c6fc
--- /dev/null
+++ b/srcpkgs/ncgopher/template
@@ -0,0 +1,17 @@
+# Template file for 'ncgopher'
+pkgname=ncgopher
+version=0.4.0
+revision=1
+build_style=cargo
+hostmakedepends="ncurses-devel openssl-devel pkg-config sqlite-devel"
+depends="ncurses"
+short_desc="Gopher, gemini, and finger client based on ncurses"
+maintainer="Antonio Gurgel <antonio@goorzhel.com>"
+license="BSD-2-Clause"
+homepage="https://github.com/jansc/ncgopher"
+distfiles="https://github.com/jansc/ncgopher/archive/v${version}.tar.gz"
+checksum=7666222ed7e6ad811622905a86e474957350f3d3022c4548dbadbce60b91084d
+
+post_install() {
+ vlicense LICENSE
+}
next reply other threads:[~2022-08-03 1:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 1:07 Goorzhel [this message]
2022-08-03 1:09 ` [PR PATCH] [Updated] " Goorzhel
2022-08-03 2:11 ` [PR REVIEW] " classabbyamp
2022-08-03 3:13 ` [PR PATCH] [Updated] " Goorzhel
2022-08-03 3:14 ` Goorzhel
2022-08-03 3:14 ` Goorzhel
2022-08-03 3:17 ` classabbyamp
2022-08-03 3:38 ` Goorzhel
2022-08-03 3:45 ` [PR PATCH] [Updated] " Goorzhel
2022-11-02 2:14 ` github-actions
2022-11-02 2:36 ` classabbyamp
2022-11-02 15:11 ` [PR PATCH] [Updated] " Goorzhel
2023-02-02 2:01 ` github-actions
2023-02-07 2:02 ` [PR PATCH] [Closed]: " Goorzhel
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-38444@inbox.vuxu.org \
--to=goorzhel@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).