TheAssassin

We should use an environment variable, which then is usable both in standalone and plugin mode. Please see https://github.com/linuxdeploy/linuxdeploy/wiki/Plugin-system#controlling-plugin-behavior.

I'm not sure I quite understand you here. An environment implemented in linuxdeploy only has no effect in plugins at all unless they support them, too. Usually, it is preferable,...

That's got nothing to do with the AppImage, but with your outdated version of AppImageLauncher. Please install the latest 3.0 alpha (yes, despite the name, it's good for daily use).

@l3u Zstd is known for its good decompression performance, so I'm wondering how xz could be significantly faster. That said, I think 0.2s isn't a bad startup time. Zstd is...

I apologize, I didn't read your (very lengthy) statement correctly. It states correctly that the flag exists. But you are requesting xz (LZMA) support. I think that was removed by...

See https://github.com/AppImage/appimagetool/issues/69. There it's also mentioned that mksquashfs is built without xz support and bundled with appimagetool. Please open an issue at https://github.com/AppImage/appimagetool/. Edit: by the way, thanks for the...

I am sure it would be considered (given the fact that I'll be one of the reviewers of such an issue). It just needs to be well founded. Currently, we...

Interesting idea. We could use some version comparison/sorting in combination with a stable identifier such as the AppStream-introduced reverse domain names (or some to-be-invented static key). I currently do it...

This PR is unfortunately not acceptable because one cannot even tell what changes you implemented. You should never just run an autoformatter you like on an entire code base and...

Build failure is due to a change in the upstream runtime repo. Fixing this on master, rebasing afterwards.