Arch Linux User Repository

It seems that the sunshine-bin, as of today (Sep. 04, 2024), requires boost v1.83, which is now obsolete.

@escape0707 To clarify, the pacman-repo we provide has both stable and beta prebuilt packages. So effectively equivalent of AUR sunshine (un-compiled stable), sunshine-bin (compiled-stable), and sunshine-git (un-compiled beta)... but not if anyone is applying custom patches.

The repo holds the stable PKGBUILD, and downloads the beta PKGBUILD from GitHub releases.

The stable build we provide will include patches that are required for compilation, such as the recent miniupnpc patch.

I have no issue if you want to keep using this AUR repo, I just ask that anyone filing bugs try the officially provided versions first. sunshine-bin is pretty low risk though as it's basically just one of our release assets.

@LizardByte

Thank you, sir, for the information here and your effort when you helped me to solve problems at the upstream GitHub.

To my understanding, the pacman-repo you provide now is more like a -nightly build of the package and since this is a -bin package, usually the convention is to follow upstream stable release versions. The nightly build might be a good workaround to use when some breakage like this miniupnp one happen in the future. But it not that easy to track the version of it and might be a step further away from "reproducibility". As for this -bin package, maybe only bug reproducibility might be relevant, although managing tar file checksum might get harder, too. For these reasons, I think this -bin package that tracks stable release would probably still stay here for those who don't want to download nightly versions every day. In this regard, consistent upstream prebuild package support and nightly build support definitely help!

And I think sunshine-git will not be obsolete, because some AUR users might use those -git packages and add some custom patch to the build process to satisfy their own flavor. And I wish when these users encounter any problems, they will take they own responsibility to verify the issue with upstream suggested manual build procedure and confirm and provide all the info they will give independently when creating a bug report at the upstream. This effectively circumvents AUR (which basically just bash build scripts ;) ) and should satisfy the upstream requirement of probably in the future not going to accept bug encountered with some AUR packages.

Also, either version of appindicator is okay!

Thank you for clarifying this and continuously devoting your effort into this very useful software project!

Best regards!

Sorry for all the drama in the other AUR repo. Hope you brought popcorn...

We will still release an archive of the PKGBUILD as well as pre-built packages in GitHub releases going forward. We also now have our own pacman-repo, which will serve pre-built packages that are rebuilt on a daily basis. You may want to grab pre-builds from there?

This is the repo, https://github.com/LizardByte/pacman-repo

In the near future I'm planning to add the beta/pre-release to that repo as well, which may make sunshine-git and sunshine-bin obsolete.

Also, either version of appindicator is okay!

@pyamsoft

Since ayatana is installed and preferred by upstream, libappindicator-gtk3 should be dropped from the dependency list.

Thanks for the heads-up. I reverted my change of adding libappindicator-gtk3.

Future releases of the project may not include Archlinux packaged sources

From what I've read in the upstream PR, it seems that upstream will still release prebuilt binary packages. I guess we'll just stick to what we have now. And it seems that the upstream as filed an orphan / takeover request against the sunshine package, and more discussion might happen there. I hope it can go to a good direction.

Also, please note that the upstream has dropped support for Archlinux and the AUR because of maintainer burnout and online harassment. https://github.com/LizardByte/Sunshine/pull/2819

Future releases of the project may not include Archlinux packaged sources, so you may need to prepare for a future where you extract the release from one of the other releases like the DEB or RPM.

Thanks!

Hello!

A few months back I made a comment regarding adding libappindicator-gtk3 as a dependency. An upstream change has made this library optional ONLY if libayatana-appindicator is not installed. Since ayatana is installed and preferred by upstream, libappindicator-gtk3 should be dropped from the dependency list.

https://github.com/LizardByte/Sunshine/pull/2385

Thank you!

@escape707, I just update new version with patchelf for libminiupnpc.so lib.

@starscaledragon thanks for your suggestion.

@starscaledragon Good call. Last time when a similar dependency outdate issue happened there are some breaking changes between the dependency (boost lib) versions so I didn't bother. This time it seems we might be able to mitigate with the method you mentioned. Although I'm kind of busy right now (moving to a new place without fibre net installed yet). Could the package owner @chungn take a look at this if you are still around?

@escape0707 you can add patchelf as makedepends and run patchelf --replace-needed libminiupnpc.so.17 libminiupnpc.so.18 sunshine to solve the dependency issue