Re: PrismLauncher: update to 7.1.

[SpidFightFR <SpidFightFR@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]

New comment by SpidFightFR on void-packages repository

https://github.com/void-linux/void-packages/pull/44326#issuecomment-1595718328

Comment:
back again on this PR, i changed the commit and the title of the PR as i used the template i made this morning for my prismlauncher installation.

Just in case, the first message stays true:

#### Testing the changes
- I tested the changes in this PR: **YES**


#### Local build testing
- I built this PR locally for my native architecture, (x64-GlibC)


#### Additional notes for the PR
- Kept the changes with openjdk, i can confirm it works.
- We should stay on QT5 (`-DLauncher_QT_VERSION_MAJOR='5'` argument), as PrismLauncher both supports QT5 and QT6. Switching to QT6 brings nothing really useful, but it does bring **issues with the plasma5 D.E**, especially in terms of theming. So like i said earlier, we should remain this argument for as long as Plasma staying on QT5. Once plama QT6 is out, we could add the changes provided by @classabbyamp (https://github.com/void-linux/void-packages/pull/44326#issuecomment-1584977013).
- ~~When building PrismLauncher, it also builds PolyMC~~, that should not be happening and we should fix this. Those two launchers are **separated** launchers, and PolyMC can even bring security issues related to specific changes brought by it's main maintainer.