Github messages for voidlinux
 help / color / mirror / Atom feed
From: flupe <flupe@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: soju-0.2.1
Date: Mon, 04 Oct 2021 10:12:51 +0200	[thread overview]
Message-ID: <20211004081251.U-8hILL19rqJXDWi868gxqVjd7VAG-EHHbCHkyfaJko@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33302@inbox.vuxu.org>

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

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

https://github.com/flupe/void-packages master
https://github.com/void-linux/void-packages/pull/33302

New package: soju-0.2.1
<!-- Mark items with [x] where applicable -->

#### General
- [x] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (ARCH-LIBC)


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

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

From 6214cfcb8efdd68422120d1b21814d1b60285efb Mon Sep 17 00:00:00 2001
From: flupe <lucas@escot.me>
Date: Sun, 3 Oct 2021 23:37:05 +0200
Subject: [PATCH] New package: soju-0.2.1

---
 srcpkgs/soju/files/soju/run |  6 ++++++
 srcpkgs/soju/template       | 31 +++++++++++++++++++++++++++++++
 2 files changed, 37 insertions(+)
 create mode 100755 srcpkgs/soju/files/soju/run
 create mode 100644 srcpkgs/soju/template

diff --git a/srcpkgs/soju/files/soju/run b/srcpkgs/soju/files/soju/run
new file mode 100755
index 000000000000..fba505701928
--- /dev/null
+++ b/srcpkgs/soju/files/soju/run
@@ -0,0 +1,6 @@
+#!/bin/sh
+if [ -f /etc/soju/config ]; then
+  CONF="-config /etc/soju/config"
+fi
+[ -r conf ] && . ./conf
+exec chpst -u soju:soju soju $CONF 2>&1
diff --git a/srcpkgs/soju/template b/srcpkgs/soju/template
new file mode 100644
index 000000000000..9b66f2d764c6
--- /dev/null
+++ b/srcpkgs/soju/template
@@ -0,0 +1,31 @@
+# Template file for 'soju'
+pkgname=soju
+version=0.2.1
+revision=1
+build_style=gnu-makefile
+hostmakedepends="go scdoc"
+short_desc="User-friendly IRC bouncer"
+maintainer="flupe <lucas@escot.me>"
+license="AGPL-3.0-or-later"
+homepage="https://git.sr.ht/~emersion/soju"
+changelog="${homepage}/refs/v${version}"
+distfiles="${homepage}/refs/download/v${version}/${pkgname}-${version}.tar.gz"
+checksum=3558db9f78da3d0311b45e42307ef01af3218156b0370d85a1d7eef4d2811559
+conf_files="/etc/soju/config"
+system_accounts="soju"
+soju_homedir="/var/lib/soju"
+make_dirs="/var/lib/soju 0755 soju soju"
+
+do_build() {
+	export CGO_CPPFLAGS="${CPPFLAGS}"
+	export CGO_CFLAGS="${CFLAGS}"
+	export CGO_CXXFLAGS="${CXXFLAGS}"
+	export CGO_LDFLAGS="${LDFLAGS}"
+	GOFLAGS="-buildmode=pie -trimpath -ldflags=-linkmode=external -mod=readonly -modcacherw"
+	make ${makejobs} PREFIX="${DESTDIR}"/usr GOFLAGS="${GOFLAGS}"
+}
+
+post_install() {
+	vlicense LICENSE
+	vsv soju
+}

  parent reply	other threads:[~2021-10-04  8:12 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-03 21:43 [PR PATCH] " flupe
2021-10-03 22:52 ` Vaelatern
2021-10-04  8:12 ` flupe [this message]
2021-10-04  8:14 ` flupe
2021-10-04 11:14 ` [PR REVIEW] " flupe
2021-10-04 11:24 ` paper42
2021-10-04 11:27 ` paper42
2021-10-04 12:41 ` [PR PATCH] [Updated] " flupe
2021-10-04 12:47 ` flupe
2021-10-04 16:31 ` Duncaen
2021-10-04 16:32 ` Duncaen
2021-10-04 18:13 ` flupe
2021-10-04 18:49 ` flupe
2021-10-04 19:28 ` [PR PATCH] [Updated] " flupe
2021-10-04 19:30 ` flupe
2021-10-04 19:39 ` Duncaen
2021-10-04 21:25 ` [PR PATCH] [Updated] " flupe
2021-10-04 21:26 ` flupe
2021-10-04 21:50 ` [PR REVIEW] " Duncaen
2021-10-04 22:52 ` flupe
2021-10-04 22:58 ` [PR PATCH] [Updated] " flupe
2021-10-04 23:33 ` [PR REVIEW] " Duncaen
2021-10-04 23:35 ` Duncaen
2021-10-04 23:35 ` Duncaen
2021-10-05 10:26 ` [PR PATCH] [Updated] " flupe
2021-11-20 22:57 ` Duncaen
2021-11-20 22:58 ` Duncaen
2021-11-21  8:42 ` [PR PATCH] [Updated] " flupe
2021-11-21  8:48 ` flupe
2021-11-21  8:53 ` New package: soju-0.3.0 flupe
2021-11-21 17:35 ` [PR PATCH] [Merged]: " Vaelatern

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=20211004081251.U-8hILL19rqJXDWi868gxqVjd7VAG-EHHbCHkyfaJko@z \
    --to=flupe@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).