Github messages for voidlinux
 help / color / mirror / Atom feed
From: heppu <heppu@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: fnm-1.35.1
Date: Fri, 05 Apr 2024 14:13:08 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49718@inbox.vuxu.org> (raw)

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

There is a new pull request by heppu against master on the void-packages repository

https://github.com/heppu/void-packages new-pkg/fnm
https://github.com/void-linux/void-packages/pull/49718

New package: fnm-1.35.1
#### 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
- I built this PR locally for these architectures:
  - x86_64-musl
  - aarch64
  - aarch64-musl
  - armv6hf-musl
  - armv6hf
  - armv6l-musl
  - armv6l
  - armv7hf-musl
  - armv7hf
  - armv7l-musl
  - armv7l


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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-pkg/fnm-49718.patch --]
[-- Type: text/x-diff, Size: 1261 bytes --]

From e88cbd164bc8334251f8ec9e6e2b82c601c00e22 Mon Sep 17 00:00:00 2001
From: Henri Koski <henri.t.koski@gmail.com>
Date: Fri, 5 Apr 2024 14:25:05 +0300
Subject: [PATCH] New package: fnm-1.35.1

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

diff --git a/srcpkgs/fnm/template b/srcpkgs/fnm/template
new file mode 100644
index 00000000000000..a286505d58dd9c
--- /dev/null
+++ b/srcpkgs/fnm/template
@@ -0,0 +1,23 @@
+# Template file for 'fnm'
+pkgname=fnm
+version=1.35.1
+revision=1
+build_style=cargo
+build_helper=qemu
+hostmakedepends="pkg-config"
+makedepends="libzstd-devel"
+short_desc="Fast and simple Node.js version manager, built in Rust"
+maintainer="Henri Koski <henri.t.koski@gmail.com>"
+license="GPL-3.0"
+homepage="https://github.com/Schniz/fnm"
+changelog="https://raw.githubusercontent.com/Schniz/fnm/master/CHANGELOG.md"
+distfiles="https://github.com/Schniz/fnm/archive/refs/tags/v${version}.tar.gz"
+checksum=df0f010f20e6072a8a52365f195cc94c35ebaf486cc285948e10eabf768d17ba
+
+post_install() {
+	for shell in bash fish zsh; do
+		vtargetrun ${DESTDIR}/usr/bin/fnm completions --shell ${shell} > fnm.${shell}
+		vcompletion fnm.${shell} ${shell}
+	done
+}
+

             reply	other threads:[~2024-04-05 12:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 12:13 heppu [this message]
2024-04-05 18:30 ` [PR PATCH] [Updated] " heppu
2024-04-07 11:11 ` heppu
2024-04-07 11:37 ` classabbyamp
2024-04-07 14:01 ` heppu
2024-05-20  6:10 ` [PR PATCH] [Updated] " heppu

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49718@inbox.vuxu.org \
    --to=heppu@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).