From: meator <meator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: dry-0.11.1
Date: Sun, 17 Jul 2022 14:36:01 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38106@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
There is a new pull request by meator against master on the void-packages repository
https://github.com/meator/void-packages dry
https://github.com/void-linux/void-packages/pull/38106
New package: dry-0.11.1
I've included a flag in `go_ldflags` that sets the version, but `dry` also expects `github.com/moncho/dry/version.GITCOMMIT` to contain the git revision of `dry`. I haven't included it because using git to retreive it from the version tag or explicitly specifying the commit in a custom variable isn't worth it in my opinion. Because of this, `dry -v` now shows:
```
dry version 0.11.1, build
```
without a newline at the end.
#### 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**
A patch file from https://github.com/void-linux/void-packages/pull/38106.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-dry-38106.patch --]
[-- Type: text/x-diff, Size: 1013 bytes --]
From f266ef65a8e1a1290b906036eab6e1eb71d8f61b Mon Sep 17 00:00:00 2001
From: meator <meator.dev@gmail.com>
Date: Sun, 17 Jul 2022 14:14:59 +0200
Subject: [PATCH] New package: dry-0.11.1
---
srcpkgs/dry/template | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
create mode 100644 srcpkgs/dry/template
diff --git a/srcpkgs/dry/template b/srcpkgs/dry/template
new file mode 100644
index 000000000000..3fe7bb35d62d
--- /dev/null
+++ b/srcpkgs/dry/template
@@ -0,0 +1,17 @@
+# Template file for 'dry'
+pkgname=dry
+version=0.11.1
+revision=1
+build_style=go
+go_import_path=github.com/moncho/dry
+go_ldflags="-X github.com/moncho/dry/version.VERSION=${version}"
+short_desc="Docker manager for the terminal"
+maintainer="meator <meator.dev@gmail.com>"
+license="MIT"
+homepage="https://moncho.github.io/dry/"
+distfiles="https://github.com/moncho/dry/archive/refs/tags/v${version}.tar.gz"
+checksum=69547e0167db8bf4b1536cdc007d6d27c787f53d5e1662e67adca99600e34435
+
+post_install() {
+ vlicense LICENSE
+}
next reply other threads:[~2022-07-17 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 12:36 meator [this message]
2022-07-17 16:39 ` classabbyamp
2022-07-17 17:08 ` [PR PATCH] [Updated] " meator
2022-07-17 17:09 ` meator
2022-10-16 2:14 ` github-actions
2022-10-16 18:14 ` [PR PATCH] [Closed]: " meator
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-38106@inbox.vuxu.org \
--to=meator@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).