[PR PATCH] New package: pounce 1.4p1

[PR PATCH] New package: pounce 1.4p1

[PaperMountainStudio]

[-- 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

Re: [PR PATCH] [Updated] New package: pounce 1.4p1

[PaperMountainStudio]

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

There is an updated 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 0c8acd49cc404f56f59f09160442d1804cf7b71c 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.4p2

---
 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..b2566af6f6f
--- /dev/null
+++ b/srcpkgs/pounce/template
@@ -0,0 +1,14 @@
+# Template file for 'pounce'
+pkgname=pounce
+version=1.4p2
+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=488edcb2c2fd23565800cab96c409ff17900d1a61ffb900ea4080afffd3d7141

Re: [PR PATCH] [Merged]: New package: pounce 1.4p2

[leahneukirchen]

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

There's a merged pull request on the void-packages repository

New package: pounce 1.4p2
https://github.com/void-linux/void-packages/pull/24244

Description:
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`

Re: New package: pounce 1.4p2

[leahneukirchen]

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

New comment by leahneukirchen on void-packages repository

https://github.com/void-linux/void-packages/pull/24244#issuecomment-678658320

Comment:
Users may want to use catsit or their own svscan tree.