Github messages for voidlinux
 help / color / mirror / Atom feed
From: yoshiyoshyosh <yoshiyoshyosh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: ferium-4.3.4
Date: Tue, 07 Mar 2023 15:51:33 +0100	[thread overview]
Message-ID: <20230307145133.iTVZLCY7ixjuE8fpArI_kljORUim93S3d0a-G4h3B88@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42637@inbox.vuxu.org>

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

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

https://github.com/yoshiyoshyosh/void-packages ferium
https://github.com/void-linux/void-packages/pull/42637

New package: ferium-4.3.4
#### 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):
  - armv7l (crossbuild)

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

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

From 438edb5cbba64dd11ffc15bd8ee651cb354cb78e Mon Sep 17 00:00:00 2001
From: yosh <yosh-git@riseup.net>
Date: Mon, 6 Mar 2023 23:48:38 -0500
Subject: [PATCH] New package: ferium-4.3.4

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

diff --git a/srcpkgs/ferium/template b/srcpkgs/ferium/template
new file mode 100644
index 000000000000..1172a26d95bf
--- /dev/null
+++ b/srcpkgs/ferium/template
@@ -0,0 +1,21 @@
+# Template file for 'ferium'
+pkgname=ferium
+version=4.3.4
+revision=1
+build_style=cargo
+build_helper=qemu
+short_desc="CLI program for managing Minecraft mods and modpacks"
+maintainer="yosh <yosh-git@riseup.net>"
+license="MPL-2.0"
+homepage="https://github.com/gorilla-devs/ferium"
+changelog="https://raw.githubusercontent.com/gorilla-devs/ferium/main/CHANGELOG.md"
+distfiles="https://github.com/gorilla-devs/ferium/archive/refs/tags/v${version}.tar.gz"
+checksum=7f5fab2141a03c6fcf22dac2349331f2a478a48677d91defc545406ce70f7aca
+
+post_install() {
+	local ferium="${DESTDIR}/usr/bin/ferium"
+	for shell in bash fish zsh; do
+		vtargetrun ${ferium} complete ${shell} > ferium.${shell}
+		vcompletion ferium.${shell} ${shell}
+	done
+}

  parent reply	other threads:[~2023-03-07 14:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07  4:55 [PR PATCH] " yoshiyoshyosh
2023-03-07 10:26 ` tranzystorek-io
2023-03-07 11:34 ` [PR REVIEW] " tranzystorek-io
2023-03-07 14:22 ` [PR PATCH] [Updated] " yoshiyoshyosh
2023-03-07 14:37 ` [PR REVIEW] " tranzystorek-io
2023-03-07 14:41 ` tranzystorek-io
2023-03-07 14:42 ` yoshiyoshyosh
2023-03-07 14:51 ` yoshiyoshyosh [this message]
2023-04-26 21:07 ` [PR PATCH] [Updated] " yoshiyoshyosh
2023-06-24 13:44 ` [PR PATCH] [Merged]: New package: ferium-4.4.0 Duncaen

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=20230307145133.iTVZLCY7ixjuE8fpArI_kljORUim93S3d0a-G4h3B88@z \
    --to=yoshiyoshyosh@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).