From: akhiljalagam <akhiljalagam@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: microsocks-1.0.3
Date: Thu, 15 Sep 2022 09:25:58 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39296@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
There is a new pull request by akhiljalagam against master on the void-packages repository
https://github.com/akhiljalagam/void-packages microsocks
https://github.com/void-linux/void-packages/pull/39296
New package: microsocks-1.0.3
<!-- 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, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/39296.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-microsocks-39296.patch --]
[-- Type: text/x-diff, Size: 1151 bytes --]
From b338975a1d29204f2e9e6639fbb30c3deca4aeb6 Mon Sep 17 00:00:00 2001
From: akhil <akhil.j@outlook.in>
Date: Thu, 15 Sep 2022 12:52:15 +0530
Subject: [PATCH] New package: microsocks-1.0.3
---
srcpkgs/microsocks/template | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
create mode 100644 srcpkgs/microsocks/template
diff --git a/srcpkgs/microsocks/template b/srcpkgs/microsocks/template
new file mode 100644
index 000000000000..e7b42ac6bd41
--- /dev/null
+++ b/srcpkgs/microsocks/template
@@ -0,0 +1,20 @@
+# Template file for 'microsocks'
+pkgname=microsocks
+version=1.0.3
+revision=1
+build_style=gnu-makefile
+short_desc="Tiny, portable SOCKS5 server with very moderate resource usage"
+maintainer="akhil <akhil.j@outlook.in>"
+license="MIT"
+homepage="https://github.com/rofl0r/microsocks"
+changelog="https://github.com/rofl0r/microsocks/releases"
+distfiles="https://github.com/rofl0r/microsocks/archive/refs/tags/v${version}.tar.gz"
+checksum=6801559b6f8e17240ed8eef17a36eea8643412b5a7476980fd4e24b02a021b82
+
+pre_build() {
+ sed -i 's|prefix = /usr/local|prefix = /usr|' Makefile
+}
+
+post_install() {
+ vlicense COPYING
+}
next reply other threads:[~2022-09-15 7:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 7:25 akhiljalagam [this message]
2022-12-15 2:02 ` github-actions
2022-12-30 1:58 ` [PR PATCH] [Closed]: " github-actions
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-39296@inbox.vuxu.org \
--to=akhiljalagam@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).