From: JohnGebbie <JohnGebbie@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: gek-0.1
Date: Sun, 03 Jul 2022 17:19:39 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37817@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
There is a new pull request by JohnGebbie against master on the void-packages repository
https://github.com/JohnGebbie/void-packages gek
https://github.com/void-linux/void-packages/pull/37817
New package: gek-0.1
#### 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-packagegs/blob/master/Manual.md#quality-requirements): **YES**
A patch file from https://github.com/void-linux/void-packages/pull/37817.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-gek-37817.patch --]
[-- Type: text/x-diff, Size: 1019 bytes --]
From 215ef3e5241845d48266314d3d3b9b0955b1cd4e Mon Sep 17 00:00:00 2001
From: John Gebbie <me@johngebbie.com>
Date: Sun, 3 Jul 2022 16:03:25 +0100
Subject: [PATCH] New package: gek-0.1
---
srcpkgs/gek/template | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
create mode 100644 srcpkgs/gek/template
diff --git a/srcpkgs/gek/template b/srcpkgs/gek/template
new file mode 100644
index 000000000000..0da6033a30a3
--- /dev/null
+++ b/srcpkgs/gek/template
@@ -0,0 +1,26 @@
+# Template file for 'gek'
+pkgname=gek
+version=0.1
+revision=1
+hostmakedepends="git go"
+short_desc="Stack-based stream editor and scripting language"
+maintainer="John Gebbie <me@johngebbie.com>"
+license="GPL-3.0-only"
+homepage="https://geklang.org/"
+
+do_fetch() {
+ git clone https://git.sr.ht/~geb/gek "${wrksrc}"
+ cd "${wrksrc}"
+}
+
+do_build() {
+ go build -o gek ./src
+}
+
+do_install() {
+ vbin gek
+ vbin gekdoc
+ vman gek.1
+ mkdir "${DESTDIR}/usr/share/doc"
+ cp -r doc "${DESTDIR}/usr/share/doc/${pkgname}"
+}
next reply other threads:[~2022-07-03 15:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 15:19 JohnGebbie [this message]
2022-07-03 16:23 ` [PR REVIEW] " classabbyamp
2022-07-03 16:23 ` classabbyamp
2022-07-03 17:13 ` [PR PATCH] [Updated] " JohnGebbie
2022-07-03 17:18 ` [PR REVIEW] " JohnGebbie
2022-07-03 17:23 ` classabbyamp
2022-07-03 17:49 ` JohnGebbie
2022-07-03 17:56 ` classabbyamp
2022-07-03 17:56 ` paper42
2022-07-03 17:57 ` classabbyamp
2022-07-03 19:32 ` [PR PATCH] [Updated] " JohnGebbie
2022-07-03 19:34 ` [PR REVIEW] " JohnGebbie
2022-07-03 21:20 ` paper42
2022-07-03 21:53 ` [PR PATCH] [Updated] " JohnGebbie
2022-07-03 21:58 ` [PR REVIEW] " JohnGebbie
2022-07-03 22:00 ` paper42
2022-07-04 8:03 ` [PR PATCH] [Updated] " JohnGebbie
2022-07-04 8:04 ` [PR REVIEW] " JohnGebbie
2022-07-05 8:32 ` JohnGebbie
2022-07-05 13:42 ` classabbyamp
2022-07-05 14:11 ` [PR PATCH] [Updated] " JohnGebbie
2022-07-05 14:15 ` [PR REVIEW] " paper42
2022-07-05 18:00 ` [PR PATCH] [Updated] " JohnGebbie
2022-09-29 18:34 ` JohnGebbie
2022-09-29 18:34 ` [PR PATCH] [Closed]: " JohnGebbie
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-37817@inbox.vuxu.org \
--to=johngebbie@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).