Github messages for voidlinux
 help / color / mirror / Atom feed
From: Cornelius-Figgle <Cornelius-Figgle@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: pipes-rs-1.6.1
Date: Sat, 12 Aug 2023 08:55:09 +0200	[thread overview]
Message-ID: <20230812065509.yvWDyKXgN5D13t4iie6gBs5t21EXcibzGTP6WIlGeXw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45555@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 693 bytes --]

There is an updated pull request by Cornelius-Figgle against master on the void-packages repository

https://github.com/Cornelius-Figgle/void-packages add_pipes-rs
https://github.com/void-linux/void-packages/pull/45555

New package: pipes-rs-1.6.1
#### Testing the changes
- I tested the changes in this PR: **briefly**

#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**

#### Local build testing
- I built this PR locally for my native architecture, aarch64-glibc


A patch file from https://github.com/void-linux/void-packages/pull/45555.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-add_pipes-rs-45555.patch --]
[-- Type: text/x-diff, Size: 1072 bytes --]

From 633f78fc1ae3b0d5fbdf1870f0863e17184f4ab3 Mon Sep 17 00:00:00 2001
From: Cornelius-Figgle <max@fullimage.net>
Date: Fri, 11 Aug 2023 21:56:28 +0100
Subject: [PATCH] New package: pipes-rs-1.6.1

---
 srcpkgs/pipes-rs/template | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)
 create mode 100644 srcpkgs/pipes-rs/template

diff --git a/srcpkgs/pipes-rs/template b/srcpkgs/pipes-rs/template
new file mode 100644
index 0000000000000..82bd8bf56d842
--- /dev/null
+++ b/srcpkgs/pipes-rs/template
@@ -0,0 +1,16 @@
+# Template file for 'pipes-rs'
+pkgname=pipes-rs
+version=1.6.1
+revision=1
+build_style=cargo
+make_install_args="--path crates/pipes-rs"
+short_desc="Over-engineered rewrite of pipes.sh"
+maintainer="Cornelius-Figgle <max@fullimage.net>"
+license="BlueOak-1.0.0"
+homepage="https://github.com/lhvy/pipes-rs"
+distfiles="https://github.com/lhvy/pipes-rs/archive/refs/tags/v${version}.tar.gz"
+checksum=93e2b8e8afb6e8ecde20bf3b4fab6e9dc4abeacbf7d2065929611d2c43cf8638
+
+if [ "$XBPS_TARGET_NO_ATOMIC8" ]; then
+    XBPS_CROSS_RUSTFLAGS+=" -latomic"
+fi

  reply	other threads:[~2023-08-12  6:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 21:01 [PR PATCH] " Cornelius-Figgle
2023-08-12  6:55 ` Cornelius-Figgle [this message]
2023-08-12  7:11 ` [PR PATCH] [Updated] " Cornelius-Figgle
2023-08-12 11:18 ` Cornelius-Figgle
2023-08-12 11:28 ` Bnyro
2023-08-12 11:28 ` Bnyro
2023-08-12 11:31 ` [PR PATCH] [Updated] " Cornelius-Figgle
2023-08-13 18:06 ` Cornelius-Figgle
2023-08-13 18:08 ` [PR PATCH] [Closed]: " Cornelius-Figgle
2023-08-13 18:08 ` [PR PATCH] [Updated] " Cornelius-Figgle
2023-08-13 18:16 ` Cornelius-Figgle

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=20230812065509.yvWDyKXgN5D13t4iie6gBs5t21EXcibzGTP6WIlGeXw@z \
    --to=cornelius-figgle@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).