[Feature Request] Add --appimage-enum-binaries to enumerate embedded binaries

[KurtPfeifle]

I think there is a need to allow users to list the embedded binaries which can be started depending on what the name of ${0} (or argv[0] for a compiled program) is when the AppImage is invoked.

Currently there are already a few AppImages on the "market" which support and make use of the feature to embed multiple binaries. But it is not easy to enumerate them (I know I could run appimagetool --list the.AppImage | grep bin/, but...)

The fact that this is even possible has escaped many developers' attention, even if they had already pondered to use AppImage for the distribution their own applications (see for example this comment).

So the binaries inside an AppImage should be made more easily discoverable. One first step could be to implement a new parameter

 --appimage-enum-binaries    # Enumerate all startable binaries embedded in AppImage

[probonopd]

The more generic case would be --appimage-list usr/bin/*... if we implement --appimage-list

[KurtPfeifle]

This command feels a bit too complicated to expose to users this way... I'm not against implementing this however. OTOH, people who would use that very likely will be able to also run --appimage-list | grep /any/path/.

[azubieta]

IMHO the different entry points of an AppImage should be exposed by the desktop integration functions. This is a topic to discuss at AppImageCommunity/appimaged#30

[probonopd]

We need to be clear that there is always one main entry point that is executed when the application is double-clicked. I am not aware that the systems described in AppImageCommunity/appimaged#30 allow for more one entry point.