To respond to your previous comment though, I do like the idea of warning users who lack Java 8 a lot and I think that'd be the best compromise. Since Ubuntu is still carrying openjdk-8-jre, perhaps it would be good to split the Debian and Ubuntu packages? The Ubuntu package could continue depending on Java 8 for maximum compatibility, and the Debian package could depend on default-jre, just so it brings in something at I'm not involved with the MultiMC project and can't merge it myself, I apologize. It just means that no Java version will be brought in at all. Right now, the Ubuntu package (with the Qt fix, at least) works fine on Debian since openjdk-8-jre is only a recommendation and not a dependency. Ultimately, it's an issue of retaining compatibility for older versions of the game, which will definitely be a major concern as long as 1.12 is "the version for modding." Maybe it'll be easier to bring in a newer Java version once the most popular version of the game for modding is >=1.16.
#MULTIMC JAVA 8 INSTALL#
Worth mentioning that this fix has been included by default in Fabric Loader for a while as well, so all Fabric 1.16 instances work fine with recent Java versions without needing to install anything extra: FabricMC/fabric#1176
#MULTIMC JAVA 8 MOD#
It is however perfectly fine for >=1.13 with the Fabric mod Voyager installed, which fixes the CME. With that in mind, it almost wouldn't be a bad idea to stop including Java with MultiMC for Debian and leave it to the user to find a preferred version and install it. The Java issue will remain a bit of an issue though, since there is no trivial way at the moment to run 1.12 and lower with Java >8, compounded by the LWJGL 2->3 switch which had other implications. I agree that the Qt issue should probably be split off since it has a much less controversial fix. I guess a PPA could also be automatically added which includes a version of Java 8 like the official Minecraft launcher does, but that might cause package conflicts.
Java 8 is still supported for now so it would be ideal to find a way to include that, but seeing as Debian appear to have made their decision about Java 8 efforts should probably be focused on finding the best compromise to support Java 11 or not including Java at all. Sorry, I've updated my comment to reflect that. Install an instance of Debian Unstable (instructions).ĭownload the 1.4-1 version of the MultiMC. Steps to reproduce the issue (Add more if needed): This points to the Java runtime recommended for the user's distro version and CPU architecture, which will usually be Java 11 on Debian 10+ or Ubuntu 18.04+ (which should still be compatible with any recent Minecraft/Forge/Fabric version), or Java 8 on Debian <9 or Ubuntu <16.04. It should also recommend the default-jre package instead of openjdk-8-jre. As far as I can tell, this should just be libqt5widgets5 libqt5gui5 libqt5network5 libqt5core5a libqt5xml5 libqt5concurrent5
The MultiMC package should depend on the specific Qt libraries it requires, instead of qt5-default. Similarly, Ubuntu is only carrying it in the universe repo (as a consequence of inheriting its packages from Debian Unstable) so it lacks Canonical support. MultiMC also recommends the openjdk-8-jre package which is bad practice, and won't work at all in Debian which has deprecated it outside of unstable.
The MultiMC package will soon be uninstallable with Debian 11 and Ubuntu 21.04, and it already is uninstallable with Debian Sid/Unstable.
#MULTIMC JAVA 8 ARCHIVE#
The qt5-default package that MultiMC depends on is being removed after a long time of packages in the Debian/Ubuntu archive already not being allowed to depend on it. Operating System: Debian Sid/Unstable Summary of the issue or suggestion: MultiMC version: N/A (The relevant version of the Debian package is 1.4-1)
0 kommentar(er)
