Why use AppRun?


#1

Hi again!

I try to understand how best to organize the contents in my AppDir (which imo should get its own wiki page describing its structure).

One of the questions that arise is, what is the benefit of the AppRun binary over just using a shell script or even a symlink to the application binary?

In this thread Simon says this is perfectly possible:

However the AppImage would then miss the --appimage-xyz options, that a user might know from different AppImages and expect to be present:

My thoughts:

  • Are there any other benefits of using the provided AppRun binary?

  • Will there be further options in the future? Like the integration of the update mechanism directly into the AppImage?

  • Shouldn’t it be declared a best practice to always bundle the provided AppRun to guarantee a consistent behaviour across all AppImages?

Thanks and keep up the great work!


#2

Thanks for the hint; added that page.

You can use a shell script or a symlink to the main executable, or the AppRun provided by AppImageKit. It really doesn’t matter as long as your AppRun file or symlink is capable of launching the main payload application correctly.

Using the AppRun provided by AppImageKit takes care of launching the payload application for you in many cases, so it can save you from doing manual boilerplate code.

The AppRun file has nothing to do with the update mechanism. From our side we consider the AppRun provided by AppImageKit to be feature complete; if people have additional requirements they are welcome to write their own AppRun file (or extend the one in AppImageKit).

Not needed, since the only requirement of an AppRun file or symlink is to launch the main payload application. Every additional feature is a “specialty” of the respective AppImage and not something that all AppImages will (or should) support.

Code that should be common to all AppImages does not go into AppRun, but into runtime.c.

These are not handled by AppRun but by runtime.c.

Remember that AppRun is an AppDir thing (predating AppImage and useable outside of AppImages) while runtime.c is an additional thing introduced by AppImage.


#3

This was my main misconception! I thought, AppRun was somehow important for the AppImage “header”, but of course it is part of the iso payload!

Thanks for clarifying! :slight_smile: