Good news for Linux and Steam Deck fans, the yuzu team have worked to bring the installer for the Nintendo Switch Emulator over to Linux properly.
This was a bit of a sore spot, while you could still install it relatively easily having the proper installer just puts another tick in the box for making it that bit simpler for everyone. Why have they done it now though? As they said previously it was mostly Windows users playing with it but over time they've seen "consistent growth in the number of our Linux users" and so it was only natural for them to improve their own support of Linux.
This new installer supports Mainline and Early Access builds for Linux users. With Early Access builds being available for their Patreon supporters.
The work was done by a user going by the handle toastUnlimited. As with any new thing, it might have some issues so be sure to report any you find.
#!/bin/bash -x
OUTDIR=/home/$USER/apps/appimages
ID=$(curl -s -H "Accept: application/vnd.github.v3+json" https://api.github.com/repos/pineappleEA/pineapple-src/releases/latest | jq '.assets | map(select(.name=="yuzu-x86_64.AppImage"))[].id')
curl -H "Accept: application/octet-stream" -L https://api.github.com/repos/pineappleEA/pineapple-src/releases/assets/$ID -o "$OUTDIR/Yuzu.AppImage"
chmod +x "$OUTDIR/Yuzu.AppImage"
Last edited by dibz on 12 August 2022 at 2:19 pm UTC
Quoting: dibzAlternatively I wrote this little bash script to update yuzu (early access) if anyone wants it. Requires jq and curl to be installed.This, and I would prefer using the distro package manager, it's easier.
#!/bin/bash -x
OUTDIR=/home/$USER/apps/appimages
ID=$(curl -s -H "Accept: application/vnd.github.v3+json" https://api.github.com/repos/pineappleEA/pineapple-src/releases/latest | jq '.assets | map(select(.name=="yuzu-x86_64.AppImage"))[].id')
curl -H "Accept: application/octet-stream" -L https://api.github.com/repos/pineappleEA/pineapple-src/releases/assets/$ID -o "$OUTDIR/Yuzu.AppImage"
chmod +x "$OUTDIR/Yuzu.AppImage"
Probably it's because I'm using linux for some years, that I think that using the package manager it's easier than searching on internet for an installer, downloading it, executing it, and follow an assistant.
Quoting: jordicomaQuoting: dibzAlternatively I wrote this little bash script to update yuzu (early access) if anyone wants it. Requires jq and curl to be installed.This, and I would prefer using the distro package manager, it's easier.
#!/bin/bash -x
OUTDIR=/home/$USER/apps/appimages
ID=$(curl -s -H "Accept: application/vnd.github.v3+json" https://api.github.com/repos/pineappleEA/pineapple-src/releases/latest | jq '.assets | map(select(.name=="yuzu-x86_64.AppImage"))[].id')
curl -H "Accept: application/octet-stream" -L https://api.github.com/repos/pineappleEA/pineapple-src/releases/assets/$ID -o "$OUTDIR/Yuzu.AppImage"
chmod +x "$OUTDIR/Yuzu.AppImage"
Probably it's because I'm using linux for some years, that I think that using the package manager it's easier than searching on internet for an installer, downloading it, executing it, and follow an assistant.
Agreed, system package manager any day of the week. AppImages, Flatpaks, Snaps, all seem to be the current (unfortunate) hotness and all of them are sub-par compared to native packaging.
Quoting: jordicomaThis, and I would prefer using the distro package manager, it's easier.
Probably it's because I'm using linux for some years, that I think that using the package manager it's easier than searching on internet for an installer, downloading it, executing it, and follow an assistant.
For awhile now, I have been using the flatpak version of yuzu from flathub so that it would integrate with my GUI package manager and CLI scripts. Appimages are fine (barring some rare/random incompatibles with Fedora), but FOSS has truly spoiled me to expect all of my updates in one place!
Last edited by Numeric on 12 August 2022 at 4:24 pm UTC
Quoting: dibzAgreed, system package manager any day of the week. AppImages, Flatpaks, Snaps, all seem to be the current (unfortunate) hotness and all of them are sub-par compared to native packaging.
Flatpak IS a package manager, you know. It’s just that it’s a lot more robust than the legacy traditional ones (dnf, apt, pacman, etc).
Quoting: fireplaceQuoting: dibzAgreed, system package manager any day of the week. AppImages, Flatpaks, Snaps, all seem to be the current (unfortunate) hotness and all of them are sub-par compared to native packaging.
Flatpak IS a package manager, you know. It’s just that it’s a lot more robust than the legacy traditional ones (dnf, apt, pacman, etc).
There's a reason I said system/native. Not everyone likes flatpaks or appimages, and some people do. There are pluses and minuses to using something like a flatpak and the same is true for system/native.
Quoting: MilaniumDo you really need a GUI updater for AppImages?
AppImages are unfortunately painful to update. There are GUIs and even daemons out there that can do it, but typically the appimage itself has to be built in a way that supports updating. Yuzu actually is built (now) with support for that sort of thing, so no, it doesn't actually need a different way if you have one of those general appimage update tools installed -- they're not by default. Some apps even support this type of updating built-in, which is nice. Duckstation is another one that supports generic updating, but for example, avidemux's appimage does not and you have to download updates manually.
Quoting: dibzYeah. I went through years of fiddling back in the day when there was no option, grinding through dependencies to finally get to the rpm I actually was trying to install. Things finally got to where they Just Work and I can function while just paying attention mainly to very few sources that only require a click, and I have no interest in going back. Nowadays, if it's not in the Mint Software Manager (or on Steam) it's pretty close to might as well not exist, for me.Quoting: jordicomaQuoting: dibzAlternatively I wrote this little bash script to update yuzu (early access) if anyone wants it. Requires jq and curl to be installed.This, and I would prefer using the distro package manager, it's easier.
#!/bin/bash -x
OUTDIR=/home/$USER/apps/appimages
ID=$(curl -s -H "Accept: application/vnd.github.v3+json" https://api.github.com/repos/pineappleEA/pineapple-src/releases/latest | jq '.assets | map(select(.name=="yuzu-x86_64.AppImage"))[].id')
curl -H "Accept: application/octet-stream" -L https://api.github.com/repos/pineappleEA/pineapple-src/releases/assets/$ID -o "$OUTDIR/Yuzu.AppImage"
chmod +x "$OUTDIR/Yuzu.AppImage"
Probably it's because I'm using linux for some years, that I think that using the package manager it's easier than searching on internet for an installer, downloading it, executing it, and follow an assistant.
Agreed, system package manager any day of the week. AppImages, Flatpaks, Snaps, all seem to be the current (unfortunate) hotness and all of them are sub-par compared to native packaging.
I don't have a huge problem with Flatpaks in theory--mild ambivalence, but not like hostility. So if some game's Steam package is actually a Flatpak, or my Software Manager installs a Flatpak, OK, cool. But I'm not going to add a new, uncurated software source like Flathub to my software sources that might not play well with my existing stuff, and I'm not going to start messing with maintaining a bunch of separate software with separate downloads and launchers. Don't get me wrong, it's nice they made a launcher, it's a good step, but unless I have a really compelling reason that's still not quite at the stage where I'm going to use a piece of software. Not even because it would be hard to install, I'm sure it's quite easy. It's just clutter to lose track of, a source of conflicting dependencies, I don't want that kind of mess.
Last edited by Purple Library Guy on 12 August 2022 at 8:02 pm UTC
See more from me