Why list libraries? about appimage-builder HOT 4 CLOSED

Hi @koendv consider that appimage-builder is under heavy development so right now the features are far from being stable. Regarding your question, would you mind to add a bit more of context of what you purpose to add/remove/change and why?
Thanks

from appimage-builder.

If you were talking about the embed software tracking. It refers to embedding along with the binaries the information of their source so user can validate that.

from appimage-builder.

OK.
The AppImage contains the libraries needed to run the binary.
You can list these libraries in the .yml recipe, but most of the time you can generate a reasonable list of libraries automatically. Run ldd on the binary, and you get a list of the libraries that binary dynamically links with.

For an example, look at OpenScad AppImage, under "Create AppImage". In bash copying all needed libraries is something like this:

LIBS=$(ldd usr/bin/your_binary_here | sed -e 's/^.* => //' -e 's/ (0x.*$//' | grep '/usr/')
for L in $LIBS
do
  cp --preserve $L $INSTALL_ROOT/usr/lib/
done

Basically, I'd have appimage-builder choose a reasonable default for the libraries if nothing is specified.

from appimage-builder.

I guess that your request is already implemented. We run ld.so -list on every elf file deployed in the AppDir to identify and bundle in it's dependencies. But this method is not capable of locating the libraries that are loaded using dlopen (A.K.A. plugins).

The dpkg> includes section is designed to manually list those packages that provide resources (not only libraries) that cannot be located using the ldd way.

You can see an example here

If fulfilled your request please close the issue otherwise feel free to keep asking :)

from appimage-builder.