Arch Linux User Repository

So yea, I just tested it and your package works just fine for me with OpenJDK. I just removed the lines around "if [[ "$CARCH" == 'x86_64' ]]"

The start-up script just starts "java" so it'll use the default JVM on your system (configurable with archlinux-java or just modify /usr/bin/mage-client and /usr/bin/mage-server to point to the version you like.) For me, that's OpenJDK 11 and it's actually running fine using both OpenJDK 11 and OpenJDK 8.

EDIT: It is giving some errors about OpenJFX on OpenJDK 11 so the "What's new" page doesn't work. Changing /usr/bin/mage-client to point to /usr/lib/jvm/java-8-openjdk/bin/java fixed it though.

Is this bundled (and outdated) JRE really needed? I've been contributing to xmage upstream and it builds and runs just fine for me inside IntelliJ IDEA using the OpenJDK 8 from the Arch repo (1.8.0_265 at time of writing.)

I haven't tried packaging a release version yet but I may give it a try in a bit.

DMN: The xmage.desktop file is in the directory above the srcdir, I had forgotten to indicate that in the PKGBUILD as ../xmage.desktop. It is now fixed

Aidonius, on update I'm getting:

  -> installing icon and .desktop file...
install: cannot stat 'xmage.desktop': No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...

I think it's just because xmage.desktop needs including in the $source array for it to be copied into $srcdir (I modified the PKGBUILD locally like that which resolved it) but I'm not overly familiar with PKGBUILDs.

Adonius: I've been running xmage-server under java-1.8.0-openjdk-armhf just fine with only hiccoughs I cannot positively attribute to the JRE (likely, card implementation bugs). I have not attempted to run xmage-client on my RPi under thst JRE yet (and likely won't - my whole need for avoiding the launcher's workaround, aside from architecture mismatch, is headless daemonization - which, wink wink nudge nudge, would be a nice systemd unit file to write and package :P)

As you can see in the Github thread, java-1.11.0-openjdk-armhf fairly obviously does not work (although it does start - it just rejects connections, as that is where the then-illegal reflective access occurs).

Beacon515L: The reason why the package supplies its own version of java is because xmage requires not just openjre 1.8, but 8u201. This version is not and has not been available in the Arch Linux repositories. If you are able to make xmage work with a version available in the archives, please notify me and I will see what I can do with the package.

I have updated the PKGBUILD to depend on jre8-openjdk(any version) on all architectures excluding x86_64. This replaces the dedicated java installation on non x86_64 machines. Behaviour on x86_64 machines has not changed. I built the package on my ARM machine as well(aarch64) without any problems. I have not tested it however. Also, the versions of jre8-openjdk in the Arch Linux ARM repositories do not appear to be versions that are compatible with xmage, but I have not tested this. Please notify me if you have any success.

MAGE's documentation is incorrect - the Java version must be exactly 8, not merely 7+. The server breaks down with illegal reflective access violations in Java 9 and higher.

The supplied JRE works around it, but 1) only for x64 and 2) is possibly an Oracle TOS violation as of the TOS changes of 2019-04-19 which I have taken up with the developers.

Since your package declares an architecture of 'any' (which any good Java application package in principle should), I reccommend restore a dependency on OpenJRE 1.8 and let pacman sort it out - because right now your package is broken on ARM.

My discussion with the dev is here: https://github.com/magefree/mage/issues/5862

muffehazard: Done, thank you for the heads up

Please add wget as a make dependency

trigun0x2: I have removed the version requirement from the PKGBUILD. The xmage git page specifies that the installed Java version be 7 or greater, so the version requirement was unneeded. In order to execute xmage, you run the commands mage-client or mage-server.