Saying goodbye to Qt 5 about prismlauncher HOT 10 OPEN

For the sake of this RFC, I propose dropping them for 9.0

Windows-MSVC-Legacy was already dropped in 8.0

from prismlauncher.

I think simply removing the bin package from the aur (...) would be a sufficient solution for now

this wouldn't be "simple", as any user at any time could revive it. there's also the chance of a malicious actor adopting the package and distributing their own binaries, which would have to be from a source besides us, as ours don't work. this is a risk i don't think we can take

or marking it as broken

there isn't a way to do this on the aur as far as i know? but we still have tried to make sure everyone is aware here

I'm sorry but dismissing this as an "arch problem" is not very helpful

of course not, but there isn't much we really can do to help. the aur isn't exactly meant for binaries
alternatives like making our own binary distribution specifically for arch also aren't really viable, as abi breakages are very common

in the OP it's stated that you want to switch once the "vast majority" of users have a good experience with Qt6

i wouldn't consider this an issue with qt 6, but a distribution one. qt 6 itself will give you a great experience on more viable platforms for binaries like the chaotic aur, flathub, etc.

from prismlauncher.

Qt 6 is still broken on archlinux: #991

from prismlauncher.

arch problem, compile prismlauncher yourself with the source aur package, it's not on our side that arch broke ABI compatibility

from prismlauncher.

Or use the AppImage/Flatpak packages. -bin packages are inherently broken, and no Arch package maintainer wanted to pick up Prism Launcher into the main repos.

from prismlauncher.

To add to this, even upstream Qt thinks it's a bad idea (see https://bugreports.qt.io/browse/QTBUG-112332?focusedId=786408&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-786408). Maybe we should just deprecate the prebuilt tarball and start shipping Qt in our portable builds

from prismlauncher.

I'm sorry but dismissing this as an "arch problem" is not very helpful. Even if a problem is not your responsibility, in the OP it's stated that you want to switch once the "vast majority" of users have a good experience with Qt6. Making sure that there is a solution to this problem is I think part of that.

from prismlauncher.

You can use chaotic aur if you do not want to build prism yourself: https://github.com/chaotic-aur where you have either the latest release or the git package(the nightly builds): https://pkgs.org/download/prismlauncher

from prismlauncher.

I think simply removing the bin package from the aur (or marking it as broken) would be a sufficient solution for now.

from prismlauncher.

Maybe we should just deprecate the prebuilt tarball and start shipping Qt in our portable builds

i think this would be a good way to go. not much breakage either, since i really don't know of any downstream packages that use it besides prismlauncher-{,qt5-}bin

maybe something for a new issue?

from prismlauncher.