probonopd

I see. Would the ability to just specify a different path (but not filename) be sufficient for your use case?

Hi @CalebQ42. We would want static binaries for all supported architectures of go-appimage. This probably means that we will need to build our own, like we do with the other...

Well. Is there even a dwarfs filesystem for golang that we could use?

Well, so far the draft of the AppImageSpec does not specify any particular filesystem format for type-2 AppImages, but the plan has been since a while to standardize on squashfs...

If we then also manage to also have [static builds of the runtime](https://github.com/AppImage/AppImageKit/issues/877) and AppRun, then we are no longer dependent on Docker containers with ancient build host systems at...

> That is not a "complaint about AppImage", because third parties don't have to work with this infrastructure, and the tools can be built just fine on modern OSes. The...

There are now experimental AppImages using a static runtime and containing only static binaries. In theory, they should be able to run on non-glibc systems and on systems with very...

...and we are running on __NixOS__ 

The latest https://github.com/AppImage/type2-runtime/releases/tag/continuous has the static runtime. We have changed a lot there. If you want to try: https://github.com/AppImage/appimagetool/releases/tag/continuous uses it. Remaining task: In the appimagetool AppImage, put all needed...

Need to build `file` statically https://github.com/alpinelinux/aports/blob/master/main/file/APKBUILD Need to build `appstreamcli` statically https://github.com/alpinelinux/aports/blob/master/main/file/APKBUILD Also see https://github.com/Azathothas/Toolpacks/tree/main/.github/scripts/x86_64_Linux/bins/appstreamcli.sh References: * https://github.com/probonopd/go-appimage/issues/272 * https://github.com/probonopd/static-tools/pull/47