Add pre-packaged Linux builds to releases

[marvin1099]

Description of the feature

It seems you have already added Linux compile to GitHub workflows, but there is probably some issue with that, I'm guessing.

Why should this be implemented

So it would be nice if the auto build for Linux would be activated / fixed, so it can show as a GitHub release option.

Additional information

If nothing else, it would be nice to at least know, what the problem is that is stopping the Linux auto build.

[TeamSpen210]

The problem is that I don’t really know the correct way to package something so that it can be installed on Linux, which distributions to target, etc..

[marvin1099]

Makes scene, I have to try it to be sure but I think the package that pyinstaller spits out is a universal Linux package,
I think all that would be needed is a compile on Debian or something similar and will work on Ubuntu, Debian and Arch. Then just package it up in a zip or tar, like you do for the windows version.
I will check to make sure if that would in fact work. I get back later.

Edit: I think its universal, but it I don't think it fully builds all the all the library's to compiled files. So after compile it asked me where a library file is on my Debian VM.
Maby it just isn't universal as i first thought, in any case I would say just target Debian, then it will be compatible with the distros that are targeted at beginners (eg. Ubuntu or Linux Mint).
Those are my thoughts so far, maby I will try some other things, but for now I think that's fine. I think it would be nice to have a Debian option, or to at least to consider it.

[soupermkc]

Could have it in AppImage form, since that seems universal enough Linux wise. Would probably work as it'd have it's own bundled libraries isolated from the system itself.

[vrad-exe]

I think I'm going to start directing people here for problems related to linux packaging, currently there's like multiple different issues open for it, and since the steam deck came out a couple years ago and now windows 10 reached its end of support it seems like there's been a lot more people wanting to run BEE on linux then there was historically.

[ThaBluNate]

The "best" individual package format is probably AppImage (completely self-contained, runs on nearly anything, though can be wasteful), and/or just a tarball with binaries inside /w a list of required dependencies (less wasteful, although it would work much like the windows build)

[marvin1099]

Both the tarball and the appimage would be selfcontaned and probably what this project would want to use.
Only issue right now ist that there is no building mode that would keep all the dependencys around.
At least that is want i think the issue is since last time i tryed to compile on one system and run on another one it did not work.
That would have to be sorted out, so it can be put into a tarball or into an appimage.
Anyway just what i think, if someone can figure this out it would be great.

[Coke-Unity]

Flatpack is made to work on most linux distros as long as your system has flatpack installed.

[marvin1099]

@Coke-Unity but since flatpak is sandboxed by defaut it probably more difficut to make it work via flatpak. Pacageing for appimage is just get all libs with binarys in a zip like file and it just works.