From: PaperMountainStudio <PaperMountainStudio@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: pounce 1.4p1
Date: Wed, 12 Aug 2020 19:20:48 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24244@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]
There is a new pull request by PaperMountainStudio against master on the void-packages repository
https://github.com/PaperMountainStudio/void-packages new-package-pounce
https://github.com/void-linux/void-packages/pull/24244
New package: pounce 1.4p1
Pounce package contains 2 executables - `calico` and `pounce`. `pounce` is a bouncer which can connect only to **one** network. `pounce` usually listens on a unix socket and `calico` listens on a TCP port dispatching connections to running instances of pounce.
For example `znc` can connect to multiple networks at once, so it makes sense to have a service file for it. Should `pounce` or `calico` have sv services? I don't think it would make sense for pounce since users will probably have to have multiple service files with different command in each one. `calico` service doesn't make sense too, because there is not a standard location of pounce unix sockets, it has to be configured by users.
An alternative would be adding example service files in `/usr/share/examples`
A patch file from https://github.com/void-linux/void-packages/pull/24244.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-package-pounce-24244.patch --]
[-- Type: text/x-diff, Size: 998 bytes --]
From 012a9cd15e4e3158a2414920288edb5738bf949b Mon Sep 17 00:00:00 2001
From: Paper <paper@tilde.institute>
Date: Wed, 12 Aug 2020 16:33:56 +0200
Subject: [PATCH] New package: pounce 1.4p1
---
srcpkgs/pounce/template | 14 ++++++++++++++
1 file changed, 14 insertions(+)
create mode 100644 srcpkgs/pounce/template
diff --git a/srcpkgs/pounce/template b/srcpkgs/pounce/template
new file mode 100644
index 00000000000..85f7d833fed
--- /dev/null
+++ b/srcpkgs/pounce/template
@@ -0,0 +1,14 @@
+# Template file for 'pounce'
+pkgname=pounce
+version=1.4p1
+revision=1
+build_style=gnu-configure
+make_build_target="all"
+hostmakedepends="pkg-config"
+makedepends="libressl-devel"
+short_desc="Multi-client, TLS-only IRC bouncer"
+maintainer="Paper <paper@tilde.institute>"
+license="GPL-3.0-or-later"
+homepage="https://git.causal.agency/pounce/"
+distfiles="https://git.causal.agency/pounce/snapshot/pounce-$version.tar.gz"
+checksum=11d509aa1f7a7ecb2e84056f91f7bc9cf1ea6a286f7657c8967684dd8302638a
next reply other threads:[~2020-08-12 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 17:20 PaperMountainStudio [this message]
2020-08-17 11:48 ` [PR PATCH] [Updated] " PaperMountainStudio
2020-08-22 16:02 ` [PR PATCH] [Merged]: New package: pounce 1.4p2 leahneukirchen
2020-08-22 16:02 ` leahneukirchen
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-24244@inbox.vuxu.org \
--to=papermountainstudio@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).