summarylogtreecommitdiffstats
path: root/PKGBUILD
AgeCommit message (Collapse)Author
2023-01-26Update to 22.3.1Lucas Werkmeister
2022-10-25Update to 22.3.0, rename to graalpy-jdk11-binLucas Werkmeister
Upstream renamed from GraalPython to GraalPy, so rename the package accordingly. Also, there’s an AArch64 version now.
2022-07-26Update to 22.2.0Lucas Werkmeister
2022-05-21Add some library packages to dependsLucas Werkmeister
AUR user mjacob [1] reported [2] that libxcrypt-compat is required to run graalpython; checking with strace revealed that gcc-libs and zlib are probably also required (though they’re more likely to be installed already), so let’s add those too. [1]: https://aur.archlinux.org/account/mjacob/ [2]: https://aur.archlinux.org/packages/graalpython-jdk17-bin#comment-865963
2022-04-26Update to 22.1.0Lucas Werkmeister
Remove lib/installer/components/org.graalvm.component, it’s already in jdk11-graalvm-bin and including it here makes the install fail.
2022-01-25Update to 22.0.0.2Lucas Werkmeister
2021-10-19Update to 21.3.0Lucas Werkmeister
2021-07-20Update to 21.2.0Lucas Werkmeister
2021-04-20Update to 21.1.0Lucas Werkmeister
2021-02-14Update to 21.0.0.2Lucas Werkmeister
2021-01-19Update to 21.0.0Lucas Werkmeister
2020-11-17Update to 20.3.0Lucas Werkmeister
2020-08-19Update to 20.2.0Lucas Werkmeister
2020-05-22Update to 20.1.0Lucas Werkmeister
2020-03-07Don’t try to copy missing fileLucas Werkmeister
This file was renamed from 3rd_party_licenses_graalpython.txt to THIRD_PARTY_LICENSE_GRAALPYTHON.txt with the 20.0.0 release; in the previous commit, I had added the new name, but not removed the old one. This didn’t result in an error locally because makepkg doesn’t clean the srcdir by default, so the file was still there. AUR user florensie [1] noticed the mistake. [1]: https://aur.archlinux.org/account/florensie/
2020-02-19Update to 20.0.0Lucas Werkmeister
2020-01-15Update to 19.3.1Lucas Werkmeister
2020-01-04Update to 19.3.0.2Lucas Werkmeister
2019-11-25Initial commitLucas Werkmeister
With the 19.3.0 release, GraalVM supports two Java versions: Java 8 and Java 11. This also affects all sibling packages, including GraalPython, so the former graalpython-bin package is split in two: graalpython-jdk8-bin and graalpython-jdk11-bin (this package). We use this opportunity to make several other adjustments as well. We no longer provide a version of the package name without the “-bin” suffix. It doesn’t seem likely that a built-from-source version will be added to the AUR soon, and other packages like jdk8-openj9-bin or jdk8-j9-bin don’t provide non-bin versions either. To make it possible to install graalpython-jdk8-bin and graalpython-jdk11-bin in parallel, the symlink in /usr/bin is removed (as it would otherwise conflict between the two packages). Users can add /usr/lib/jvm/default/bin/ or a similar directory to their $PATH, or otherwise ensure that they can still run the right graalpython without specifying its full path. And finally, a .gitignore file never hurts.