ArchImage VS arch2appimage

In primis, see how to install/download archimage-cli at https://github.com/ivan-hc/ArchImage , I've also released a brief video on the README (the main page) of the repository (I use Handbrake as an example). Enjoy your customizations;

I'm creating AppImages based on JuNest (Arch Linux-based distro), at https://github.com/ivan-hc/ArchImage

This is the repo https://github.com/ivan-hc/ArchImage

So I merged JuNest and AppImages and I've done ArchImage.

Arch2AppImage is useless, just like my Arch-Deployer (Arch2AppImage is inspired by my project, see it's README), I've also created an "issue" on its repository to explain why I've abandoned it, see https://github.com/hanzala123/arch2appimage/issues/25 ).

I'm a creator of AppImage packages, the basis always used (and recommended) is to create them based on old distributions for compatibility reasons. With this solution I want to try to break that rule. Both my Arch-deployer and the better known arch2appimage failed at this (and were archived as a result).

less than two years ago I published a bash script that can that downloads a package from the Arch repository or from ChaoticAUR with all its dependences, and this was a big success for me on this community and on github. Later someone else, inspired by this project, have developed its own tool with a better code and easier to use (DT on YouTube did also a review on it, here). Everithing is great, I'm glad about all this, but... I stopped work on my repo more than 1 year ago (about december 2021) for a reason, the same that I think the developer of arch2appimage have understand later (and I said it into an issue, here), that's why its project have no more commits since 9 months. Arch-based AppImages are not a good idea, here are two reasons:

If you are in Arch, arch2appimage can easily make packages from Chaotic AUR.