From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: chirp-20190524
Date: Sat, 01 Jun 2019 22:14:56 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12072@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 437 bytes --]
There is a new pull request by acobaugh against master on the void-packages repository
https://github.com/acobaugh/void-packages chirp
https://github.com/void-linux/void-packages/pull/12072
New package: chirp-20190524
Is there a policy regarding naming/versioning of packages that are "daily" releases? This tool has no other style of release.
A patch file from https://github.com/void-linux/void-packages/pull/12072.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-chirp-12072.patch --]
[-- Type: application/text/x-diff, Size: 1162 bytes --]
From e72bec47df30be48f840f10b4b77ef580d6ed6ff Mon Sep 17 00:00:00 2001
From: Andy Cobaugh <andrew.cobaugh@gmail.com>
Date: Sat, 1 Jun 2019 16:13:29 -0400
Subject: [PATCH] New package: chirp-20190524
---
srcpkgs/chirp/template | 14 ++++++++++++++
1 file changed, 14 insertions(+)
create mode 100644 srcpkgs/chirp/template
diff --git a/srcpkgs/chirp/template b/srcpkgs/chirp/template
new file mode 100644
index 00000000000..634b03b2791
--- /dev/null
+++ b/srcpkgs/chirp/template
@@ -0,0 +1,14 @@
+# Template file for 'chirp'
+pkgname=chirp
+version=20190524
+revision=1
+build_style=python2-module
+hostmakedepends="python-devel python-pyserial libxml2-python"
+makedepends="python-devel python-pyserial python-lxml pygtk-devel libxml2-python"
+short_desc="CHIRP is a free, open-source tool for programming your amateur radio."
+maintainer="Andy Cobaugh <andrew.cobaugh@gmail.com>"
+license="GPL-3.0"
+homepage="https://chirp.danplanet.com"
+distfiles="https://trac.chirp.danplanet.com/chirp_daily/daily-${version}/chirp-daily-${version}.tar.gz"
+wrksrc="${pkgname}-daily-${version}"
+checksum=90246dbd9afa19579ee5aef1c8501d39f945bb87732ee60ee1dfda289ceb59cf
next reply other threads:[~2019-06-01 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-01 20:14 voidlinux-github [this message]
2019-06-02 0:50 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-02 0:50 ` voidlinux-github
2019-06-04 13:49 ` voidlinux-github
2019-06-04 13:49 ` [PR PATCH] [Closed]: " voidlinux-github
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-12072@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--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).