From: tranzystorek-io <tranzystorek-io@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: bkt-0.5.3
Date: Sat, 19 Mar 2022 07:00:24 +0100 [thread overview]
Message-ID: <20220319060024.Uy53ZMFqhSCie22iyg8JK77n8Sdt3OP7uapKE4xnbbU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36124@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]
There is an updated pull request by tranzystorek-io against master on the void-packages repository
https://github.com/tranzystorek-io/void-packages bkt
https://github.com/void-linux/void-packages/pull/36124
New package: bkt-0.5.3
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](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/36124.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-bkt-36124.patch --]
[-- Type: text/x-diff, Size: 913 bytes --]
From 9935dc865653ca551ed33df5ff27ae1746958246 Mon Sep 17 00:00:00 2001
From: Marcin Puc <marcin.e.puc@gmail.com>
Date: Sun, 13 Mar 2022 23:28:29 +0100
Subject: [PATCH] New package: bkt-0.5.3
---
srcpkgs/bkt/template | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
create mode 100644 srcpkgs/bkt/template
diff --git a/srcpkgs/bkt/template b/srcpkgs/bkt/template
new file mode 100644
index 000000000000..e7a0e3fcb722
--- /dev/null
+++ b/srcpkgs/bkt/template
@@ -0,0 +1,16 @@
+# Template file for 'bkt'
+pkgname=bkt
+version=0.5.3
+revision=1
+build_style=cargo
+short_desc="Subprocess caching utility"
+maintainer="Marcin Puc <marcin.e.puc@gmail.com>"
+license="MIT"
+homepage="https://www.bkt.rs/"
+distfiles="https://github.com/dimo414/bkt/archive/${version}.tar.gz"
+checksum=38c418e8abe1bf6835f1b16d02c03677075af6b10ad4723392540ec79797520e
+
+post_install() {
+ vlicense LICENSE
+ vdoc README.md
+}
next prev parent reply other threads:[~2022-03-19 6:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 22:31 [PR PATCH] New package: bkt-0.5.2 tranzystorek-io
2022-03-14 9:11 ` [PR PATCH] [Updated] " tranzystorek-io
2022-03-16 18:50 ` [PR PATCH] [Updated] New package: bkt-0.5.3 tranzystorek-io
2022-03-19 5:40 ` tranzystorek-io
2022-03-19 6:00 ` tranzystorek-io [this message]
2022-03-26 5:42 ` tranzystorek-io
2022-03-27 19:56 ` tranzystorek-io
2022-06-07 19:03 ` tranzystorek-io
2022-06-25 20:09 ` tranzystorek-io
2022-06-25 20:27 ` [PR PATCH] [Merged]: New package: bkt-0.5.4 Duncaen
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=20220319060024.Uy53ZMFqhSCie22iyg8JK77n8Sdt3OP7uapKE4xnbbU@z \
--to=tranzystorek-io@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).