Which package should I use? #272
-
It's probably silly to ask, but I'm new to Arch aur/flatpak and stuff and I can't find info on this. Can you explain in short what the difference is between aarch64.flatpak, x86_64.flatpak and debug_x86_64.flatpak (the last one I'm pretty sure is not for me)? Why do I ask: I tried installing via PKGBUILD. It runs, but Moonlight didn't see it. I tried installing via flatpak in terminal. I'm not sure, but I think installation borked at the end. I couldn't run it from terminal, only from app menu. It worked, but version was **.dirty. But still, Moonlight didn't see it. |
Beta Was this translation helpful? Give feedback.
Replies: 0 comments 4 replies
-
Use |
Beta Was this translation helpful? Give feedback.
-
I would only use the flatpaks if the AUR modules were not working but that's a personal choice. About the different AUR options: The sunshine-bin is a good option as you don't need to wait for sunshine to build. When you say you install via PKGBUILD, are you using a helper such as yay/paru? You should know how PKGBUILD installs work but a helper will make your life easier. I have no idea why you have "dirty" packages. This isn't normal. Finally, you can try manually adding the sunshine IP address to moonlight if it is not detected. |
Beta Was this translation helpful? Give feedback.
I would only use the flatpaks if the AUR modules were not working but that's a personal choice. About the different AUR options:
sunshine - main releases
sunshine-git - nightly branch
sunshine-bin - downloads the zst from LizardByte releases and uses that.
The sunshine-bin is a good option as you don't need to wait for sunshine to build.
When you say you install via PKGBUILD, are you using a helper such as yay/paru? You should know how PKGBUILD installs work but a helper will make your life easier.
I have no idea why you have "dirty" packages. This isn't normal.
Finally, you can try manually adding the sunshine IP address to moonlight if it is not detected.