From: tranzystorek-io <tranzystorek-io@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: ymir-0.0.5
Date: Sat, 30 Sep 2023 15:16:58 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46340@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]
There is a new pull request by tranzystorek-io against master on the void-packages repository
https://github.com/tranzystorek-io/void-packages ymir
https://github.com/void-linux/void-packages/pull/46340
New package: ymir-0.0.5
<!-- Uncomment relevant sections and delete options which are not applicable -->
This is a void-centric tool for large bulk package builds. I've used it to do `build_style=cargo` rebuilds for Rust PRs.
Disclaimer: I am the author of this project.
#### 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/46340.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-ymir-46340.patch --]
[-- Type: text/x-diff, Size: 1247 bytes --]
From d5c8fc6a8980a872b914676bab487c597063dd0c Mon Sep 17 00:00:00 2001
From: Marcin Puc <tranzystorek.io@protonmail.com>
Date: Wed, 16 Aug 2023 21:42:56 +0200
Subject: [PATCH] New package: ymir-0.0.5
---
srcpkgs/ymir/template | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
create mode 100644 srcpkgs/ymir/template
diff --git a/srcpkgs/ymir/template b/srcpkgs/ymir/template
new file mode 100644
index 0000000000000..0ebb5dd42b090
--- /dev/null
+++ b/srcpkgs/ymir/template
@@ -0,0 +1,22 @@
+# Template file for 'ymir'
+pkgname=ymir
+version=0.0.5
+revision=1
+build_style=cargo
+build_helper=qemu
+short_desc="Tool for doing bulk test builds of Void Linux packages"
+maintainer="Marcin Puc <tranzystorek.io@protonmail.com>"
+license="MIT"
+homepage="https://codeberg.org/tranzystorek-io/ymir"
+changelog="https://codeberg.org/tranzystorek-io/ymir/raw/branch/main/CHANGELOG.md"
+distfiles="https://codeberg.org/tranzystorek-io/ymir/archive/v${version}.tar.gz"
+checksum=6af91fdbe20dd615269a98571302372b0245f0b99f2e4533fc8688e79bc1604d
+
+post_install() {
+ for shell in bash fish zsh; do
+ vtargetrun ${DESTDIR}/usr/bin/ymir completion ${shell} > ymir.${shell}
+ vcompletion ymir.${shell} ${shell}
+ done
+
+ vlicense LICENSE
+}
next reply other threads:[~2023-09-30 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-30 13:16 tranzystorek-io [this message]
2023-10-20 18:38 ` [PR PATCH] [Merged]: " ahesford
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-46340@inbox.vuxu.org \
--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).