As of now, the Linux GUI artifact is an AppImage file. This is achieved with linuxdeploy. The original goal was creating a fully self-contained binary, but this was never done properly (time constraints and current AppImage knowledge).
Request
Do not create an AppImage file for the GUI, as most of the dependencies are not currently embedded anyway.
It complicates the build
Fuse related issues
It may create dependency problems in certain distributions (FUSE related dependencies: i.e., fuse2 vs fuse3 vs fuse).
If the fuse libraries are not resolved, the program will silently failed to start without notice, but that's a general problem.
It doesn't "naturally" support musl .
Anticipated changes
This will impact local build scripts and the GitHub actions workflow.
README files included in zip or tar release artifacts should be updated accordingly
fuse should be removed as a dependency from any rpm spec file or deb control file.
Background
As of now, the Linux GUI artifact is an AppImage file. This is achieved with linuxdeploy. The original goal was creating a fully self-contained binary, but this was never done properly (time constraints and current
AppImage
knowledge).Request
Do not create an
AppImage
file for the GUI, as most of the dependencies are not currently embedded anyway.fuse2
vsfuse3
vsfuse
).fuse
libraries are not resolved, the program will silently failed to start without notice, but that's a general problem.musl
.Anticipated changes
spec
file or debcontrol
file.