appimagetool is out of date

[tmm1]

https://github.com/AppImageCommunity/pkg2appimage/blob/1eceb306077e51b991e987690b364e11971b44b3/functions.sh#L226C18-L226C49

this is using an obsolete build of appimagetool from march 2023: https://github.com/AppImage/AppImageKit/releases/tag/continuous

[ivan-hc]

+1 for this!

@probonopd I updated my AppImaGen tool to allow the user or upstream to choose on which base to build their AppImage and add one or more PPAs if they choose Ubuntu (any version, even the older ones, just enter the codename)

https://github.com/ivan-hc/AppImaGen

However I had to extract and repackage the current pkg2appimage to support Fuse3, using the appropriate appimagetool, and upload it to my repository.

If you could update pkg2apimage accordingly, so that upstreams can also build on the latest Ubuntu builds that do not include libfuse2 (and which can cause conflicts, once installed) that would be great.

I would much prefer to allow users to use the official pkg2appimage build, so that they can contribute to your project.

[probonopd]

AppImageCommunity = I normally only merge PRs made by the community here...

[probonopd]

@TheAssassin we also need to upload AppRun somewhere... where should it go? E.g., pkg2appimage needs it.

[TheAssassin]

@probonopd move it there then, I guess. Although it shouldn't be used there either. Also there should be a clear disclaimer that this thing is not for generic use...

[ivan-hc]

we also need to upload AppRun somewhere... where should it go? E.g., pkg2appimage needs it.

@probonopd I don't mean to be rude, but since that AppRun never worked in my Appimages (and I always had to use a script that worked poorly, mea culpa, but better than that AppRun)... I'd suggest throwing it in the trash. 😆

I'm kidding, of course. If it worked in your tests, I'd envy you. I really do.