From: damianoognissanti <damianoognissanti@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: juliaup-1.8.16
Date: Wed, 24 May 2023 10:23:57 +0200 [thread overview]
Message-ID: <20230524082357.SfilFd6WuVEzYbxDpev8-9qNf1RowJGu_0B-ZboZlU4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43906@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]
New comment by damianoognissanti on void-packages repository
https://github.com/void-linux/void-packages/pull/43906#issuecomment-1560669602
Comment:
Something like this (but please make any changes you want, and please do change the `maintainer` line, I just added something to that it wasn't empty)
```
# Template file for 'julia-bin'
pkgname=julia-bin
version=1.9.0
revision=1
only_for_archs="x86_64"
short_desc="High-level, high-performance dynamic language for technical computing"
maintainer="Damiano Ognissanti <ognissanti@hotmail.se>"
hostmakedepends="tar gzip"
license="MIT License"
homepage="https://julialang.org/"
if [ "$XBPS_TARGET_LIBC" = "musl" ]
then
distfiles="https://julialang-s3.julialang.org/bin/musl/x64/${version:0:3}/julia-${version}-musl-x86_64.tar.gz"
else
distfiles="https://julialang-s3.julialang.org/bin/linux/x64/${version:0:3}/julia-${version}-linux-x86_64.tar.gz"
fi
checksum=00c614466ef9809c2eb23480e38d196a2c577fff2730c4f83d135b913d473359
nostrip=yes
do_install() {
mkdir -p ${DESTDIR}/opt/
mkdir -p ${DESTDIR}/usr/bin/
tar xf ${XBPS_SRCDISTDIR}/${pkgname}-${version}/julia-${version}-linux-x86_64.tar.gz -C ${DESTDIR}/opt/
ln -s /opt/julia-${version}/bin/julia ${DESTDIR}/usr/bin/julia
}
```
next prev parent reply other threads:[~2023-05-24 8:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 22:27 [PR PATCH] " BryceVandegrift
2023-05-17 0:54 ` BryceVandegrift
2023-05-17 1:22 ` [PR PATCH] [Updated] " BryceVandegrift
2023-05-17 1:24 ` BryceVandegrift
2023-05-17 1:47 ` [PR REVIEW] " classabbyamp
2023-05-17 15:24 ` [PR PATCH] [Updated] " BryceVandegrift
2023-05-17 15:24 ` [PR REVIEW] " BryceVandegrift
2023-05-23 0:26 ` hervyqa
2023-05-23 0:38 ` hervyqa
2023-05-23 0:48 ` hervyqa
2023-05-23 2:15 ` hervyqa
2023-05-24 7:52 ` damianoognissanti
2023-05-24 7:53 ` damianoognissanti
2023-05-24 8:23 ` damianoognissanti [this message]
2023-05-24 8:25 ` damianoognissanti
2023-05-24 8:26 ` classabbyamp
2023-06-16 3:17 ` hervyqa
2023-06-25 21:15 ` [PR REVIEW] " classabbyamp
2023-07-03 0:53 ` BryceVandegrift
2023-07-03 1:00 ` [PR PATCH] [Updated] " BryceVandegrift
2023-07-03 1:09 ` [PR REVIEW] " BryceVandegrift
2023-07-04 9:44 ` [PR PATCH] [Updated] " classabbyamp
2023-07-04 9:56 ` [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=20230524082357.SfilFd6WuVEzYbxDpev8-9qNf1RowJGu_0B-ZboZlU4@z \
--to=damianoognissanti@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).