From: tranzystorek-io <tranzystorek-io@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: cargo-nextest-0.9.36
Date: Fri, 30 Sep 2022 20:52:45 +0200 [thread overview]
Message-ID: <20220930185245.AQutxu82G6rDOdrn4JwQ-2sf-hk4hL9zxLck-Beoki0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38224@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
There is an updated pull request by tranzystorek-io against master on the void-packages repository
https://github.com/tranzystorek-io/void-packages cargo-nextest
https://github.com/void-linux/void-packages/pull/38224
New package: cargo-nextest-0.9.36
<!-- 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**
<!-- 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/38224.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-cargo-nextest-38224.patch --]
[-- Type: text/x-diff, Size: 1459 bytes --]
From 437a2a64d66280ed71b727c944c3809d1db30013 Mon Sep 17 00:00:00 2001
From: Marcin Puc <tranzystorek.io@protonmail.com>
Date: Sat, 23 Jul 2022 22:47:30 +0200
Subject: [PATCH] New package: cargo-nextest-0.9.36
---
srcpkgs/cargo-nextest/template | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
create mode 100644 srcpkgs/cargo-nextest/template
diff --git a/srcpkgs/cargo-nextest/template b/srcpkgs/cargo-nextest/template
new file mode 100644
index 000000000000..4b8d32450330
--- /dev/null
+++ b/srcpkgs/cargo-nextest/template
@@ -0,0 +1,25 @@
+# Template file for 'cargo-nextest'
+pkgname=cargo-nextest
+version=0.9.37
+revision=1
+wrksrc="nextest-cargo-nextest-${version}"
+build_style=cargo
+configure_args="--no-default-features --features default-no-update"
+make_install_args="--path cargo-nextest"
+short_desc="Next-generation test runner for Rust"
+maintainer="Marcin Puc <tranzystorek.io@protonmail.com>"
+license="Apache-2.0, MIT"
+homepage="https://nexte.st/"
+changelog="https://raw.githubusercontent.com/nextest-rs/nextest/main/site/src/CHANGELOG.md"
+distfiles="https://github.com/nextest-rs/nextest/archive/refs/tags/cargo-nextest-${version}.tar.gz"
+checksum=3f50929b8fe098cf2ed8e2b0993983aac28a5eaf52e480ab5cba5939b0e38ab1
+
+# skip problematic tests
+case "$XBPS_TARGET_MACHINE" in
+ x86_64-musl) make_check_args="-- --skip tests_integration::test_target_dir";;
+ *) ;;
+esac
+
+post_install() {
+ vlicense LICENSE-MIT
+}
next prev parent reply other threads:[~2022-09-30 18:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 20:49 [PR PATCH] New package: cargo-nextest-0.9.28 tranzystorek-io
2022-07-23 21:24 ` [PR PATCH] [Updated] " tranzystorek-io
2022-07-24 23:15 ` tranzystorek-io
2022-07-26 4:18 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.29 tranzystorek-io
2022-07-26 4:19 ` tranzystorek-io
2022-07-26 11:30 ` New package: cargo-nextest-0.9.30 tranzystorek-io
2022-07-26 11:30 ` tranzystorek-io
2022-07-26 11:34 ` tranzystorek-io
2022-07-28 7:15 ` [PR PATCH] [Updated] " tranzystorek-io
2022-07-29 5:25 ` tranzystorek-io
2022-07-31 5:54 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.31 tranzystorek-io
2022-07-31 21:57 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.32 tranzystorek-io
2022-08-13 6:47 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.33 tranzystorek-io
2022-08-17 21:43 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.34 tranzystorek-io
2022-08-24 10:38 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.35 tranzystorek-io
2022-08-24 22:37 ` tranzystorek-io
2022-09-08 5:52 ` tranzystorek-io
2022-09-30 18:52 ` tranzystorek-io [this message]
2022-10-03 17:31 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.36 tranzystorek-io
2022-10-06 5:41 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.37 tranzystorek-io
2022-10-14 20:27 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.38 tranzystorek-io
2022-10-26 8:21 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.39 tranzystorek-io
2022-11-01 22:12 ` tranzystorek-io
2022-11-02 7:34 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.41 tranzystorek-io
2022-11-05 7:57 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.42 tranzystorek-io
2022-11-23 22:19 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.43 tranzystorek-io
2022-11-25 20:25 ` [PR PATCH] [Updated] New package: cargo-nextest-0.9.44 tranzystorek-io
2022-12-12 18:04 ` tranzystorek-io
2023-01-03 13:27 ` tranzystorek-io
2023-01-03 13:27 ` [PR PATCH] [Closed]: " tranzystorek-io
2023-01-03 13:29 ` tranzystorek-io
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=20220930185245.AQutxu82G6rDOdrn4JwQ-2sf-hk4hL9zxLck-Beoki0@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).