Allow to (bsd)tar xf instead of --appimage-extract

[oech3]

.AppImage is extracted by -appimage-extract or 7z x.

I'm not sure is it possible to support tar xf.
But tar is still useful to avoid distributing same files with 2 different format and tar has --exclude flag if supported.

[TheAssassin]

First of all, wrong repo, and this is also more of a question than an issue.

The reason why 7z works is because it apparently supports squashfs.

tar just supports tar archives, optionally compressed with algorithms like xz (LZMA).

You cannot just "add support" to the AppImage format like you suggest. You would have to make AppImages valid tar archives. And that is not possible.

[oech3]

Is actuall reason impossible to support .tar.zst is not seek-friendly?
I ref about bsdtar for recording.

[TheAssassin]

No. The issue is that it's an AppImage, not a tar archive. Please do not make up arguments.

[oech3]

What I want to know is is executable ELF+tarball possible instead of executable ELF+SquashFS.
I don't think that this project do that, but I know executable.zip is used by some projects.

[TheAssassin]

But that is not what you asked. The reason why the .zip variant works is because zip archivers should seek the file for the zip header and thus can skip over the ELF header. This does not work with tar.

[oech3]

Thankyou for answering and sorry for noise.

…

zip archivers should seek the file for the zip header and thus can skip over the ELF header. This does not work with tar.