From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] procs: update to 0.14.0
Date: Sun, 02 Apr 2023 17:30:02 +0200 [thread overview]
Message-ID: <20230402153002.P92gPFmjjT8y7H_k1WqNs33WlELtQWWDW8h_XbeRXB4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43213@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 383 bytes --]
There is an updated pull request by cinerea0 against master on the void-packages repository
https://github.com/cinerea0/void-packages procs
https://github.com/void-linux/void-packages/pull/43213
procs: update to 0.14.0
#### Testing the changes
- I tested the changes in this PR: **YES**
A patch file from https://github.com/void-linux/void-packages/pull/43213.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-procs-43213.patch --]
[-- Type: text/x-diff, Size: 1541 bytes --]
From 1c189384ce1d396fcca67aa4a29cef6ddfc31a73 Mon Sep 17 00:00:00 2001
From: cinerea0 <cinerea0@disroot.org>
Date: Sun, 2 Apr 2023 11:29:38 -0400
Subject: [PATCH] procs: update to 0.14.0
---
srcpkgs/procs/template | 16 +++++++---------
1 file changed, 7 insertions(+), 9 deletions(-)
diff --git a/srcpkgs/procs/template b/srcpkgs/procs/template
index 0713f2ac1c9b..b2455232f925 100644
--- a/srcpkgs/procs/template
+++ b/srcpkgs/procs/template
@@ -1,6 +1,6 @@
# Template file for 'procs'
pkgname=procs
-version=0.13.4
+version=0.14.0
revision=1
build_style=cargo
build_helper=qemu
@@ -10,16 +10,14 @@ license="MIT"
homepage="https://github.com/dalance/procs"
changelog="https://raw.githubusercontent.com/dalance/procs/master/CHANGELOG.md"
distfiles="https://github.com/dalance/procs/archive/refs/tags/v${version}.tar.gz"
-checksum=9b9b59b79049cf6ae2c39d9cc5b0c5af81411ba898a414fda41f68921c3c9539
-
-post_build() {
- PROCS="target/${RUST_TARGET}/release/procs"
- vtargetrun ${PROCS} --completion-out bash >procs.bash
- vtargetrun ${PROCS} --completion-out fish >procs.fish
- vtargetrun ${PROCS} --completion-out zsh >procs.zsh
-}
+checksum=fa5af0951dc8aa63c0590f8c5c1136594866057704cfb1cdfc22ac3cc49437c6
post_install() {
+ PROCS="${DESTDIR}/usr/bin/procs"
+ vtargetrun ${PROCS} --gen-completion-out bash > procs.bash
+ vtargetrun ${PROCS} --gen-completion-out fish > procs.fish
+ vtargetrun ${PROCS} --gen-completion-out zsh > procs.zsh
+
vcompletion procs.bash bash
vcompletion procs.fish fish
vcompletion procs.zsh zsh
next prev parent reply other threads:[~2023-04-02 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 15:07 [PR PATCH] " cinerea0
2023-04-02 15:12 ` [PR REVIEW] " tranzystorek-io
2023-04-02 15:30 ` cinerea0 [this message]
2023-04-02 19:15 ` [PR PATCH] [Merged]: " paper42
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=20230402153002.P92gPFmjjT8y7H_k1WqNs33WlELtQWWDW8h_XbeRXB4@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).