From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] watchexec: update to 1.23.0
Date: Fri, 01 Sep 2023 07:26:37 +0200 [thread overview]
Message-ID: <20230901052637.SW6-auSi_lcMnUVeEAblqsEryIJST5hcEIFJG1XR_VY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45856@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 391 bytes --]
There is an updated pull request by cinerea0 against master on the void-packages repository
https://github.com/cinerea0/void-packages watchexec
https://github.com/void-linux/void-packages/pull/45856
watchexec: update to 1.23.0
#### Testing the changes
- I tested the changes in this PR: **YES**
A patch file from https://github.com/void-linux/void-packages/pull/45856.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-watchexec-45856.patch --]
[-- Type: text/x-diff, Size: 1474 bytes --]
From c9ab568ca17b8421a4e622a3af9ed279d2ccb9d5 Mon Sep 17 00:00:00 2001
From: cinerea0 <cinerea0@disroot.org>
Date: Fri, 1 Sep 2023 01:26:20 -0400
Subject: [PATCH] watchexec: update to 1.23.0
---
srcpkgs/watchexec/template | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/watchexec/template b/srcpkgs/watchexec/template
index 4b8cf746d8066..1ac295a086978 100644
--- a/srcpkgs/watchexec/template
+++ b/srcpkgs/watchexec/template
@@ -1,15 +1,16 @@
# Template file for 'watchexec'
pkgname=watchexec
-version=1.22.3
+version=1.23.0
revision=1
-build_wrksrc="crates/cli"
build_style=cargo
+make_install_args="--path crates/cli"
+make_check_args="-- --skip scopes" # test fails in chroot
short_desc="Executes commands in response to file modifications"
maintainer="cinerea0 <cinerea0@protonmail.com>"
license="Apache-2.0"
homepage="https://github.com/watchexec/watchexec"
distfiles="https://github.com/watchexec/watchexec/archive/refs/tags/v${version}.tar.gz"
-checksum=698ed1dc178279594542f325b23f321c888c9c12c1960fe11c0ca48ba6edad76
+checksum=2a321962669979feef44ea7a6220819d5c916ca939eba41b033ea346a44caa90
if [ "$XBPS_TARGET_NO_ATOMIC8" ]; then
XBPS_CROSS_RUSTFLAGS+=" -latomic"
@@ -17,8 +18,8 @@ fi
post_install() {
for shell in bash fish zsh; do
- vcompletion ${wrksrc}/completions/${shell} ${shell}
+ vcompletion completions/${shell} ${shell}
done
- vman ${wrksrc}/doc/watchexec.1
+ vman doc/watchexec.1
}
next prev parent reply other threads:[~2023-09-01 5:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 19:06 [PR PATCH] " cinerea0
2023-09-01 5:26 ` cinerea0 [this message]
2023-09-07 0:46 ` [PR PATCH] [Merged]: " classabbyamp
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=20230901052637.SW6-auSi_lcMnUVeEAblqsEryIJST5hcEIFJG1XR_VY@z \
--to=cinerea0@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).