Age | Commit message (Collapse) | Author |
|
|
|
Upstream renamed from GraalPython to GraalPy, so rename the package
accordingly. Also, there’s an AArch64 version now.
|
|
|
|
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
|
|
Remove lib/installer/components/org.graalvm.component, it’s already in
jdk11-graalvm-bin and including it here makes the install fail.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|