AppImageKit VS opi

What you're looking for sounds like AppImages (https://appimage.org/) . I have only used them while downloading games from itch.io, etc. (since i prefer package managers) but they seem to work out of the box on popular distros.

Ideally a new instance of the application is installed for each user. This also provides better isolation if one user upgrades/removes/breaks their application instance. I, for one, have really come around to the AppImage model [0] in the last couple of years.

[0] https://appimage.org/

I found a similar issue on github and tried this solution but still getting the same error .

There is AppImage[1], which packs a lot of stuff into a SquashFS filesystem, appends it to the executable, so everything is in one file.

[1] https://appimage.org

Nah i think yall just hating appimage. Real gold standard.

Although I haven't used plugins feature myself yet, this does sound like the perfect use case for them. Not every patient needs to access every single source. With plugins you can load only the source (or few sources) that they actually need. You can still use something like https://appimage.org/ to give them "a single binary", but will actually contain your slim binary and all the plugins.

```dlopen(): error loading libfuse.so.2 AppImages require FUSE to run. You might still be able to extract the contents of this AppImage if you run it with the --appimage-extract option. See https://github.com/AppImage/AppImageKit/wiki/FUSE for more information```

This doesn't look like a squashfs image. Cannot mount AppImage, please check your FUSE setup. You might still be able to extract the contents of this AppImage  if you run it with the --appimage-extract option.  See https://github.com/AppImage/AppImageKit/wiki/FUSE  for more information open dir error: No such file or directory

appimages. Appimages are similar to flatpaks, exept that they are a file you download and double click to run. Think of them as portable softwares like windows has (portable apps). They are sandboxed too. You can learn more about appimages here

This is incorrect. It also installs a set list of packages.

Have you looked into OPI? This allows you to easily search and install community packages from the Open Build System similarly to how it is with working with yay on Arch. It very likely does not contain things like git packages or fonts but it can be pretty useful for packages like ckb-next and since it pulls from the OBS it is always guaranteed to be a binary, no compilation necessary

As of this writing, opi performs the following operations behind the curtains (see here for reference):

opi will implement a workaround in https://github.com/openSUSE/opi/pull/120 which will force the ffmpeg version on tumbleweed to be >=5.

OPI is your friend. You don't have to update every day...once a week or so is fine. Set up multiversion for kernels. A lot of times if a vendor offers a Fedora RPM and not openSUSE, the Fedora RPM will work fine. If you are using Nvidia, wait to update kernels... that's all I can think of. Use and update the wiki as needed, it's a good resource, but can get outdated.

Yeah I'm pretty sure it's using Packman https://github.com/openSUSE/opi

For more information https://github.com/openSUSE/opi

OPI is also useful for finding other packages that aren't in the regular repos

The easiest way to install software is with OPI, you can also search with Zypper or YaST. Generally, if you can find an RPM file built for Fedora, you can install it on Tumbleweed as well - I'm sure there are exceptions.