From: MIvanchev <MIvanchev@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: erlang-cl-1.2.4
Date: Fri, 29 Dec 2023 15:00:33 +0100 [thread overview]
Message-ID: <20231229140033.TP3is2CJUYlrgrQ7JRmPNy2dqqE10IhGCeJuqgEWwek@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47972@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 680 bytes --]
There is an updated pull request by MIvanchev against master on the void-packages repository
https://github.com/MIvanchev/void-packages erlang-cl-package
https://github.com/void-linux/void-packages/pull/47972
New package: erlang-cl-1.2.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
A patch file from https://github.com/void-linux/void-packages/pull/47972.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-erlang-cl-package-47972.patch --]
[-- Type: text/x-diff, Size: 1595 bytes --]
From e09a94a60e0966203f15bebee5e053d23f1dea54 Mon Sep 17 00:00:00 2001
From: Mihail Ivanchev <contact@ivanchev.net>
Date: Fri, 29 Dec 2023 13:21:10 +0100
Subject: [PATCH] New package: erlang-cl-1.2.4
---
srcpkgs/erlang-cl/template | 31 +++++++++++++++++++++++++++++++
1 file changed, 31 insertions(+)
create mode 100644 srcpkgs/erlang-cl/template
diff --git a/srcpkgs/erlang-cl/template b/srcpkgs/erlang-cl/template
new file mode 100644
index 0000000000000..836ed776dc983
--- /dev/null
+++ b/srcpkgs/erlang-cl/template
@@ -0,0 +1,31 @@
+# Template file for 'erlang-cl'
+pkgname=erlang-cl
+version=1.2.4
+revision=1
+hostmakedepends="git rebar3"
+makedepends="ocl-icd-devel"
+depends="erlang ocl-icd"
+short_desc="Erlang OpenCL bindings"
+maintainer="Mihail Ivanchev <contact@ivanchev.net>"
+license="MIT"
+homepage="https://github.com/tonyrog/cl"
+distfiles="https://github.com/tonyrog/cl/archive/refs/tags/cl-${version}.tar.gz"
+checksum=577b8788029148f93217d00a1bbdc500db68ee77b2246bbd892269b5bb98c41a
+
+do_build() {
+ rebar3 compile
+}
+
+do_install() {
+ vmkdir usr/lib/erlang/lib/cl-${version}
+ vmkdir usr/lib/erlang/lib/cl-${version}/ebin
+ vmkdir usr/lib/erlang/lib/cl-${version}/include
+ vmkdir usr/lib/erlang/lib/cl-${version}/priv
+ vmkdir usr/share/doc/${pkgname}
+ vmkdir usr/share/doc/${pkgname}/examples
+ vcopy ebin/* usr/lib/erlang/lib/cl-${version}/ebin
+ vinstall include/cl.hrl 644 usr/lib/erlang/lib/cl-${version}/include
+ vinstall priv/cl_nif.so 644 usr/lib/erlang/lib/cl-${version}/priv
+ vcopy examples/* usr/share/doc/${pkgname}/examples
+ vlicense COPYRIGHT
+}
next prev parent reply other threads:[~2023-12-29 14:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 13:19 [PR PATCH] " MIvanchev
2023-12-29 14:00 ` MIvanchev [this message]
2023-12-29 14:01 ` [PR PATCH] [Updated] " MIvanchev
2023-12-29 14:19 ` MIvanchev
2023-12-29 14:29 ` MIvanchev
2023-12-29 15:37 ` MIvanchev
2023-12-29 17:19 ` MIvanchev
2023-12-29 17:30 ` MIvanchev
2023-12-30 10:45 ` [PR PATCH] [Updated] " MIvanchev
2024-02-08 11:30 ` [PR PATCH] [Closed]: " MIvanchev
2024-02-08 11:30 ` MIvanchev
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=20231229140033.TP3is2CJUYlrgrQ7JRmPNy2dqqE10IhGCeJuqgEWwek@z \
--to=mivanchev@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).