Q. AppImageTool size increase and runtimes?

[kuiperzone]

I see that there is a release 1.9. Good stuff!

Q. The binary for appimagetool-x86_64.AppImage is now nearly 13 MB, whereas the older version was 2.2 MB. As I bundle the appimagetool binaries in my project, I'm curious to know the reason for the size increase?

Q. I see you discussing bundling runtimes in #61. Did you do this for version 1.9 or not?

If you didn't, I'm presuming that appimagetool would not work without an internet connection unless --runtime-file is provided? Is my understanding correct?

Thanks

[probonopd]

Hi @kuiperzone. You can run appimagetool-x86_64.AppImage --appimage-mount to inspect what is inside and what drives its size. The objective is to get it to run on as many host systems as possible with as few dependencies as possible.

[kuiperzone]

Thank you,

I obviously think making it running with few dependencies is a good idea.

But appimagetool-x86_64.AppImage --appimage-mount for 1.9.0 does nothing but hangs indefinitely on Fedora 42.

[kuiperzone]

Same for the appimagetool-x86_64.AppImage downloaded from the Continuous build.

[kuiperzone]

Nope. I'm a numpty. :)

--appimage-mount mounts the embedded filesystem image and prints the mount point, then waits until it is killed. This is useful if you would like to inspect the contents of an AppImage without executing the contained payload application

I figured it now.