Github messages for voidlinux
 help / color / mirror / Atom feed
From: reedts <reedts@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: cargo-flamegraph-0.6.2
Date: Sat, 04 Mar 2023 17:33:22 +0100	[thread overview]
Message-ID: <20230304163322.88K269Cp28dq9lKz9oWTvt7K_qwmQEEwsFA41_ab4qk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42585@inbox.vuxu.org>

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

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

https://github.com/reedts/void-packages cargo-flamegraph_v0.6.2
https://github.com/void-linux/void-packages/pull/42585

New package: cargo-flamegraph-0.6.2
<!-- 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 [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, (x86_64-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64
  - aarch64-musl
  - armv7l
  - armv7l-musl


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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-cargo-flamegraph_v0.6.2-42585.patch --]
[-- Type: text/x-diff, Size: 1338 bytes --]

From 542afa5ec5b4deb2cdaf65d2592dcaddf1f6a4b4 Mon Sep 17 00:00:00 2001
From: reedts <j.reedts@gmail.com>
Date: Sat, 4 Mar 2023 17:33:07 +0100
Subject: [PATCH] New package: cargo-flamegraph-0.6.2

---
 srcpkgs/cargo-flamegraph/template | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)
 create mode 100644 srcpkgs/cargo-flamegraph/template

diff --git a/srcpkgs/cargo-flamegraph/template b/srcpkgs/cargo-flamegraph/template
new file mode 100644
index 000000000000..73b1ef6cb52d
--- /dev/null
+++ b/srcpkgs/cargo-flamegraph/template
@@ -0,0 +1,23 @@
+# Template file for 'cargo-flamegraph'
+pkgname=cargo-flamegraph
+version=0.6.2
+revision=1
+build_style=cargo
+build_helper=qemu
+depends="perf"
+short_desc="Easy flamegraphs for Rust projects and everything else"
+maintainer="reedts <j.reedts@gmail.com>"
+license="MIT, Apache-2.0"
+homepage="https://github.com/flamegraph-rs/flamegraph"
+distfiles="https://github.com/flamegraph-rs/flamegraph/archive/refs/tags/v${version}.tar.gz"
+checksum=ec9626f8bc6e52b4c6ebbd5b35ac87f0e17e70ac1fd9eb5f26a8d7dd898f7911
+
+post_install() {
+	vlicense LICENSE-MIT
+
+	local flamegraph="${DESTDIR}/usr/bin/flamegraph"
+	for shell in bash fish zsh; do
+		vtargetrun ${flamegraph} --completions ${shell} > flamegraph.${shell}
+		vcompletion flamegraph.${shell} ${shell} flamegraph
+	done
+}

  parent reply	other threads:[~2023-03-04 16:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-04 15:27 [PR PATCH] " reedts
2023-03-04 15:32 ` [PR REVIEW] " tranzystorek-io
2023-03-04 15:35 ` tranzystorek-io
2023-03-04 15:52 ` [PR PATCH] [Updated] " reedts
2023-03-04 16:31 ` reedts
2023-03-04 16:33 ` reedts [this message]
2023-03-05  6:06 ` [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=20230304163322.88K269Cp28dq9lKz9oWTvt7K_qwmQEEwsFA41_ab4qk@z \
    --to=reedts@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).