Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: tlf-1.4.0
Date: Tue, 31 Mar 2020 02:53:03 +0200	[thread overview]
Message-ID: <20200331005303.HBXwPktd6CkLUWZII44iXgMci0MUh3ddLaLxTsO6srM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20484@inbox.vuxu.org>

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

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages tlf-1_4_0
https://github.com/void-linux/void-packages/pull/20484

New package: tlf-1.4.0


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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-tlf-1_4_0-20484.patch --]
[-- Type: text/x-diff, Size: 1628 bytes --]

From e894ff34a7427cd0dc133bb33643fe989c54c199 Mon Sep 17 00:00:00 2001
From: Abigail <dev@kb6.ee>
Date: Mon, 30 Mar 2020 18:19:34 -0400
Subject: [PATCH] New package: tlf-1.4.0

---
 srcpkgs/tlf/INSTALL.msg |  4 ++++
 srcpkgs/tlf/template    | 21 +++++++++++++++++++++
 2 files changed, 25 insertions(+)
 create mode 100644 srcpkgs/tlf/INSTALL.msg
 create mode 100644 srcpkgs/tlf/template

diff --git a/srcpkgs/tlf/INSTALL.msg b/srcpkgs/tlf/INSTALL.msg
new file mode 100644
index 00000000000..bb8862f44d8
--- /dev/null
+++ b/srcpkgs/tlf/INSTALL.msg
@@ -0,0 +1,4 @@
+Recommended optional programs:
+	xplanet: map QSOs on a globe
+	sox: handle audio for SSB contests
+	fldigi: digital modes/modem & gui/display
diff --git a/srcpkgs/tlf/template b/srcpkgs/tlf/template
new file mode 100644
index 00000000000..f08ec0bffa1
--- /dev/null
+++ b/srcpkgs/tlf/template
@@ -0,0 +1,21 @@
+# Template file for 'tlf'
+pkgname=tlf
+version=1.4.0
+revision=1
+build_style=gnu-configure
+configure_args="--datadir=/usr/share --enable-fldigi-xmlrpc"
+make_install_args="prefix=${DESTDIR}/usr datadir=${DESTDIR}/usr/share"
+hostmakedepends="automake autoconf pkg-config"
+makedepends="glib-devel hamlib-devel xmlrpc-c-devel ncurses-devel libusb-devel"
+depends="hamlib xmlrpc-c ncurses"
+checkdepends="cmocka-devel"
+short_desc="Console-based ham radio contest logger"
+maintainer="Abigail G <dev@kb6.ee>"
+license="GPL-2.0-only"
+homepage="https://tlf.github.io"
+distfiles="${NONGNU_SITE}/${pkgname}/${pkgname}-${version}.tar.gz"
+checksum=e3bac0f767b9c00ffc39f448505eadcfd57d964004c717f6dc9b3cadb36f0d7d
+
+pre_configure() {
+	autoreconf -if
+}

  parent reply	other threads:[~2020-03-31  0:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30 22:21 [PR PATCH] " classabbyamp
2020-03-30 23:13 ` [PR PATCH] [Updated] " classabbyamp
2020-03-31  0:53 ` classabbyamp [this message]
2020-03-31  2:07 ` classabbyamp
2020-03-31  3:35 ` classabbyamp
2020-03-31  3:50 ` classabbyamp
2020-03-31 16:08 ` classabbyamp
2020-10-04 20:14 ` [PR PATCH] [Closed]: " 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=20200331005303.HBXwPktd6CkLUWZII44iXgMci0MUh3ddLaLxTsO6srM@z \
    --to=classabbyamp@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).