From: chili-b <chili-b@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: tea-0.8.0
Date: Sat, 05 Mar 2022 18:20:42 +0100 [thread overview]
Message-ID: <20220305172042.IL-Gntyd3Dls4dY6YmMzMi4nfAdBUAvJN4Uab-JyR2E@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35975@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 734 bytes --]
There is an updated pull request by chili-b against master on the void-packages repository
https://github.com/chili-b/void-packages tea
https://github.com/void-linux/void-packages/pull/35975
New package: tea-0.8.0
<!-- 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 [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
A patch file from https://github.com/void-linux/void-packages/pull/35975.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-tea-35975.patch --]
[-- Type: text/x-diff, Size: 1050 bytes --]
From fbdac923c8abbc3664aef5651948b93f6efe9f1a Mon Sep 17 00:00:00 2001
From: chili-b <dexter.gaonshatford@gmail.com>
Date: Fri, 4 Mar 2022 19:16:42 -0500
Subject: [PATCH] New package: tea-0.8.0
---
srcpkgs/tea/template | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
create mode 100644 srcpkgs/tea/template
diff --git a/srcpkgs/tea/template b/srcpkgs/tea/template
new file mode 100644
index 000000000000..f529827f7c5b
--- /dev/null
+++ b/srcpkgs/tea/template
@@ -0,0 +1,19 @@
+# Template file for 'tea'
+pkgname=tea
+version=0.8.0
+revision=1
+wrksrc=$pkgname
+build_style=go
+go_import_path=code.gitea.io/tea
+depends="git"
+short_desc="Command line tool to interact with Gitea"
+maintainer="chili-b <dexter.gaonshatford@gmail.com>"
+license="MIT"
+homepage="https://gitea.io"
+changelog="https://gitea.com/gitea/tea/src/branch/master/CHANGELOG.md"
+distfiles="https://gitea.com/gitea/tea/archive/v${version}.tar.gz"
+checksum=6c73c0a7b66cdfd1e5a302257d54df06a3a41eb9bdbfeb547966db431ae23b23
+
+post_install() {
+ vlicense LICENSE
+}
next prev parent reply other threads:[~2022-03-05 17:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-05 1:25 [PR PATCH] " chili-b
2022-03-05 1:28 ` [PR PATCH] [Updated] " chili-b
2022-03-05 1:28 ` chili-b
2022-03-05 1:32 ` [PR PATCH] [Updated] " chili-b
2022-03-05 1:49 ` chili-b
2022-03-05 10:33 ` [PR REVIEW] " paper42
2022-03-05 16:32 ` [PR PATCH] [Updated] " chili-b
2022-03-05 16:34 ` [PR REVIEW] " chili-b
2022-03-05 16:35 ` [PR PATCH] [Updated] " chili-b
2022-03-05 17:02 ` [PR REVIEW] " paper42
2022-03-05 17:20 ` chili-b [this message]
2022-03-05 17:21 ` chili-b
2022-03-05 17:29 ` paper42
2022-03-05 18:07 ` [PR PATCH] [Updated] " chili-b
2022-03-05 18:07 ` [PR REVIEW] " chili-b
2022-03-08 14:10 ` paper42
2022-03-18 22:48 ` [PR PATCH] [Updated] " chili-b
2022-03-18 22:48 ` [PR REVIEW] " chili-b
2022-03-18 22:49 ` [PR PATCH] [Updated] " chili-b
2022-03-19 10:00 ` [PR PATCH] [Merged]: " paper42
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=20220305172042.IL-Gntyd3Dls4dY6YmMzMi4nfAdBUAvJN4Uab-JyR2E@z \
--to=chili-b@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).