From: jake-87 <jake-87@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: kalker-1.1.0
Date: Mon, 10 Jan 2022 06:42:21 +0100 [thread overview]
Message-ID: <20220110054221.TPzfScxYmKLha8OYMJHBHi1tqH4_Upy3PncZJe0qV2U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34975@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 665 bytes --]
There is an updated pull request by jake-87 against master on the void-packages repository
https://github.com/jake-87/void-packages master
https://github.com/void-linux/void-packages/pull/34975
New package: kalker-1.1.0
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**
#### Local build testing
- I built this PR locally for my native architecture, x84_64 GLIBC 2.32
A patch file from https://github.com/void-linux/void-packages/pull/34975.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-34975.patch --]
[-- Type: text/x-diff, Size: 1596 bytes --]
From 67f678064266b090017e6fc45db713bf806228ba Mon Sep 17 00:00:00 2001
From: jake-87 <jakehfreebsd@gmail.com>
Date: Mon, 10 Jan 2022 16:30:54 +1100
Subject: [PATCH] New package: kalker-1.1.0
---
srcpkgs/kalker/template | 32 ++++++++++++++++++++++++++++++++
1 file changed, 32 insertions(+)
create mode 100644 srcpkgs/kalker/template
diff --git a/srcpkgs/kalker/template b/srcpkgs/kalker/template
new file mode 100644
index 000000000000..ebe08b5ab170
--- /dev/null
+++ b/srcpkgs/kalker/template
@@ -0,0 +1,32 @@
+# Template file for 'kalker'
+pkgname=kalker
+version=1.1.0
+revision=1
+# Kalker fails to build on any other platform due to gmp
+# It also will not cross compile from glibc to musl, but if run on a native OS, works fine
+archs="x86_64 x86_64-musl"
+build_style=cargo
+make_install_args="--path cli"
+hostmakedepends="rust cargo gcc m4 diffutils make"
+short_desc="Kalker is a calculator with functions, derivation, and integration"
+maintainer="jake-87 <jakehfreebsd@gmail.com>"
+license="MIT"
+homepage="https://github.com/PaddiM8/kalker"
+distfiles="https://github.com/PaddiM8/kalker/archive/v${version}.tar.gz"
+checksum=4332563b18e1c2c8c54871e46f40e55791d3f86612d4651c69b690827051a484
+
+# Needed because default adds "--path ." to ${make_install_args}
+# whereas we need "--path cli"
+
+do_install() {
+ : ${make_cmd:=cargo}
+ ${make_cmd} install --target ${RUST_TARGET} --root="${DESTDIR}/usr" \
+ --locked ${configure_args} ${make_install_args}
+
+ rm -f "${DESTDIR}"/usr/.crates.toml
+ rm -f "${DESTDIR}"/usr/.crates2.json
+}
+
+post_install() {
+ vlicense LICENSE
+}
next prev parent reply other threads:[~2022-01-10 5:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 5:39 [PR PATCH] " jake-87
2022-01-10 5:42 ` jake-87 [this message]
2022-04-11 2:08 ` github-actions
2022-06-21 2:13 ` [PR PATCH] [Closed]: " github-actions
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=20220110054221.TPzfScxYmKLha8OYMJHBHi1tqH4_Upy3PncZJe0qV2U@z \
--to=jake-87@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).