sharun as the dynamic linker

[Samueru-sama]

sometimes apps break becasue they read themselves, like examples:

• https://github.com/pkgforge-dev/opencode-AppImage-Enhanced/blob/78699bad6189f9a4eb56140085166555f2c6fb4d/make-appimage.sh#L23-L32

• https://github.com/pkgforge-dev/wine-AppImage/blob/d595821125adbe3f56f4e4c74d13e08c5fc93715/make-appimage.sh#L44-L58

Would be great if we had the option to set sharun as the dynamic linker, the logic would be like this:

• lib4bin would run patchelf --set-interpreter /tmp/.sharun instead of making hardlinks.

• The binary would be copied to ${SHARUN_DIR}/bin instead of ${SHARUN-DIR}/shared/bin

• When sharun is the AppRun it would copy itself to /tmp/.sharun before jumping to exec the binaries.

• Then when /tmp/.sharun is executed by the kernel, it would figure out where the dynamic linker is by checking SHARUN_DIR and do the rest of stuff it already does.

---

I don't think we need to make this random, since sharun already is a static binary we can pick a fixed name, then sharun would be responsible for just make sure that /tmp/.sharun is present.

It may also be possible to glue sharun into the binary itself, polyfill glibc does this already, but it is likely this will break some binaries though.