zap VS appimagepool

Integrate zap with that repo and make it official. It will automatically download the appimages inside a directory 'Appimage'. You can move them anywhere else ONLY if it has a directory named 'Appimage'. In this case it is moved to an external usb.

Personally, on a debian based distribution I would either use the AppImage (you could even use something like zap to manage its version). Or, the solution I would and have personally used is to compile it from source. I am a developer, so I am biased, but the instructions are very simple and clear so it should be pretty easy to do.

That said, there is Zap.

Tho bread is github focused which is a big drawback as many software aren't on github, i discovered this program Zap Which was a appimage package manager like AM or bread but it's far much better than mine.

If you can download and install software from the web (which you also can do with debs and rpms btw), you can create a package manager to automate that from the terminal. You either trust a project or you don't, and if your don't the package format makes no difference.

NOTE: I don't know when and if to add new AppImages from the main catalog, also because a part of them is mostly broken and out of control. The AppImage packages compiled and managed by "AM"/AppMan are new AppImages that use scripts that also allow constant updating and recompilation from scratch, as if they were installed from AUR, using more reliable sources (official repositories for Debian and derivatives) . If you are interested more to the applications made available officially from the official AppImage.GitHub.io catalog, I suggest you to use Zap, Bread or the aforementioned Appimagedl. All these amazing utilities can be quickly installed via "AM" or AppMan.

I think it's safe to install it directly as it stores everything in a single directory. For AppImages there is also AppImagePool + AppImageLauncher (can be installed rootless, useful for better integration of appimages).

It's called AppImage Pool available at GitHub and in the Flathub. It also had a video done on it by TechHut.

The preferred sources for downloading packages in AppImage format via "AM" / AppMan are GitHub and Sourceforge, however, writing installation scripts that are compatible with one or more programs is a difficult task. Just think that many developers add multiple versions of the same product in the same tag (I have to include also commands to find the exact name of the latest version to avoid the download of other packages), or include more complex links that require an equally complex function to obtain the latest version of a program, and this slows down the loading of these programs on the "AM" repository I manage. I have therefore included excellent AppImage package managers such as "Bread" and "Zap" among the downloadable programs, but also "AppimagePool" and "bauh" are available among the graphics applications (not counting a "Pacstall" AppImage versionI made). These tools should compensate the lack of support for certain sources that I have not included in the "AM" repository.

I downloaded the appimage (seemed appropriate). Then marked it as executable.

Github

https://github.com/prateekmedia/appimagepool this?