From: chilledfrogs <chilledfrogs@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pounce: update to 3.1, build pounce-notify and pounce-palaver.
Date: Sat, 06 May 2023 17:13:05 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43770@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
There is a new pull request by chilledfrogs against master on the void-packages repository
https://github.com/chilledfrogs/void-packages pounce
https://github.com/void-linux/void-packages/pull/43770
pounce: update to 3.1, build pounce-notify and pounce-palaver.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- 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)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-glibc
A patch file from https://github.com/void-linux/void-packages/pull/43770.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pounce-43770.patch --]
[-- Type: text/x-diff, Size: 1240 bytes --]
From ff0789c15610d8c1800939ad50ff48d91a15d6d9 Mon Sep 17 00:00:00 2001
From: Allen Sobot <chilledfrogs@disroot.org>
Date: Sat, 6 May 2023 17:05:42 +0200
Subject: [PATCH] pounce: update to 3.1, build pounce-notify and
pounce-palaver.
---
srcpkgs/pounce/template | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/pounce/template b/srcpkgs/pounce/template
index e2cb84a05692..859b92a414f7 100644
--- a/srcpkgs/pounce/template
+++ b/srcpkgs/pounce/template
@@ -1,15 +1,16 @@
# Template file for 'pounce'
pkgname=pounce
-version=3.0
-revision=3
+version=3.1
+revision=1
build_style=gnu-configure
+configure_args="--enable-notify --enable-palaver"
make_build_target="all"
hostmakedepends="pkg-config"
-makedepends="libtls-devel"
+makedepends="libtls-devel libcurl-devel sqlite-devel"
depends="openssl"
short_desc="Multi-client, TLS-only IRC bouncer"
maintainer="Michal Vasilek <michal@vasilek.cz>"
license="GPL-3.0-or-later"
homepage="https://git.causal.agency/pounce/"
distfiles="https://git.causal.agency/pounce/snapshot/pounce-$version.tar.gz"
-checksum=f776f7f170493697a97923e7dce9597dff5577fd40ba756e9a1bcfab17199df0
+checksum=97f245556b1cc940553fca18f4d7d82692e6c11a30f612415e5e391e5d96604e
next reply other threads:[~2023-05-06 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 15:13 chilledfrogs [this message]
2023-05-17 5:27 ` [PR PATCH] [Merged]: " 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-43770@inbox.vuxu.org \
--to=chilledfrogs@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).