From: Goorzhel <Goorzhel@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: flrig-1.4.7
Date: Fri, 19 Aug 2022 02:29:04 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38771@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 517 bytes --]
There is a new pull request by Goorzhel against master on the void-packages repository
https://github.com/Goorzhel/void-packages flrig
https://github.com/void-linux/void-packages/pull/38771
New package: flrig-1.4.7
- I tested the changes in this PR: **briefly**
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
A patch file from https://github.com/void-linux/void-packages/pull/38771.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-flrig-38771.patch --]
[-- Type: text/x-diff, Size: 1042 bytes --]
From e016ee79c72579f7c3a2742f9262a369ce4b4292 Mon Sep 17 00:00:00 2001
From: Antonio Gurgel <antonio@goorzhel.com>
Date: Thu, 18 Aug 2022 17:27:24 -0700
Subject: [PATCH] New package: flrig-1.4.7
---
srcpkgs/flrig/template | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
create mode 100644 srcpkgs/flrig/template
diff --git a/srcpkgs/flrig/template b/srcpkgs/flrig/template
new file mode 100644
index 000000000000..7a57c768e68f
--- /dev/null
+++ b/srcpkgs/flrig/template
@@ -0,0 +1,17 @@
+# Template file for 'flrig'
+pkgname=flrig
+version=1.4.7
+revision=1
+build_style=gnu-configure
+makedepends="fltk-devel"
+depends="fltk"
+short_desc="Rig control program, compatible with fldigi"
+maintainer="Antonio Gurgel <antonio@goorzhel.com>"
+license="GPL-3.0-or-later"
+homepage="http://www.w1hkj.com/"
+distfiles="http://www.w1hkj.com/files/flrig/${pkgname}-${version}.tar.gz"
+checksum=473c9e25fdd3d6f29397253f10c5c563e39b92a2aaef0272041f1978a30e3b53
+
+post_install() {
+ vinstall data/flrig.desktop 644 usr/share/applications
+}
next reply other threads:[~2022-08-19 0:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 0:29 Goorzhel [this message]
2022-08-19 0:40 ` [PR REVIEW] " classabbyamp
2022-08-19 0:40 ` classabbyamp
2022-08-19 1:05 ` Goorzhel
2022-08-19 2:00 ` classabbyamp
2022-08-19 2:17 ` Goorzhel
2022-08-19 2:29 ` Goorzhel
2022-08-19 2:30 ` [PR PATCH] [Updated] " Goorzhel
2022-08-19 2:31 ` [PR REVIEW] " classabbyamp
2022-08-20 1:41 ` [PR PATCH] [Merged]: " classabbyamp
2022-08-20 1:41 ` 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-38771@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).