Github messages for voidlinux
 help / color / mirror / Atom feed
From: arbitrarygit <arbitrarygit@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: flamp-2.2.10
Date: Fri, 10 Nov 2023 07:49:42 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47144@inbox.vuxu.org> (raw)

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

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

https://github.com/arbitrarygit/void-packages flamp-2.2.10
https://github.com/void-linux/void-packages/pull/47144

New package: flamp-2.2.10
<!-- 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**

<!-- 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, x86_64-glibc and x86_64-musl
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl, crossbuild
  - armv7l, crossbuild
  - armv6l-musl, crossbuild



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

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

From d01a2247c808ed99a03c4731dabbed6278acf2e9 Mon Sep 17 00:00:00 2001
From: arbitrarygit <arbitrarygit@runbox.com>
Date: Fri, 10 Nov 2023 01:45:21 -0500
Subject: [PATCH] New package: flamp-2.2.10

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

diff --git a/srcpkgs/flamp/template b/srcpkgs/flamp/template
new file mode 100644
index 0000000000000..ce0ac407c03e5
--- /dev/null
+++ b/srcpkgs/flamp/template
@@ -0,0 +1,15 @@
+# Template file for 'flamp'
+pkgname=flamp
+version=2.2.10
+revision=1
+build_style=gnu-configure
+hostmakedepends="pkg-config"
+makedepends="fltk-devel libsamplerate-devel libXft-devel libpng-devel"
+depends="fltk"
+short_desc="Amateur radio multicast protocol application, part of fldigi suite"
+maintainer="arbitrarygit <arbitrarygit@runbox.com>"
+license="GPL-3.0-or-later"
+homepage="http://www.w1hkj.com/"
+changelog="https://sourceforge.net/p/fldigi/flamp/ci/master/tree/ChangeLog?format=raw"
+distfiles="http://www.w1hkj.com/files/flamp/${pkgname}-${version}.tar.gz"
+checksum=6f9692af7adf62b0002728a4f34854f1f1f9cca8c82ec4c3738dc908c30a4faf

             reply	other threads:[~2023-11-10  6:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-10  6:49 arbitrarygit [this message]
2023-12-03 20:11 ` [PR PATCH] [Merged]: " Duncaen

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