Skip to content

[Feature Request]: Use regular binary on Linux instead of AppImage as this is a cli program with no bundled dependencies #31

@dundarious

Description

@dundarious

Checklist

  • I have searched for a similar issue in this repository and did not find one.

Description

This project ships a commandline tool that does not need an icon or a desktop file, nor does it have any non-trivial dependencies.

As such, it should ship a plain linux executable instead of an AppImage.

Reason

I extracted the appimage contents (with --appimage-extract) and installed pkg_extractor to /usr/bin and ran ldd to show dynamic library dependencies -- this was the output:

        linux-vdso.so.1 (0x00007fa25fe29000)
        libz.so.1 => /usr/bin/../lib/libz.so.1 (0x00007fa25fc0a000)
        libstdc++.so.6 => /usr/bin/../lib/libstdc++.so.6 (0x00007fa25f800000)
        libm.so.6 => /usr/bin/../lib/libm.so.6 (0x00007fa25faec000)
        libgcc_s.so.1 => /usr/bin/../lib/libgcc_s.so.1 (0x00007fa25fabf000)
        libc.so.6 => /usr/bin/../lib/libc.so.6 (0x00007fa25f60f000)
        /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007fa25fe2b000)

These are just standard C/C++ libraries from glibc, and zlib.

In the extracted squashfs-root output from using --appimage-extract, only the following dependencies seem to be bundled:

squashfs-root/usr/optional/libstdc++.so.6/libstdc++.so.6
squashfs-root/usr/optional/libgcc_s.so.1/libgcc_s.so.1

The only other meaningful contents of squashfs-root are also not needed for a commandline tool: an icon and a desktop file.

Examples

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions