AppMan VS bread

I have been working on two CLI tools to install AppImage packages system wide and locall (they are AM and AppMan respectively). I've also written a website that acts as a catalog and a better source for downloading them all for real, https://portable-linux-apps.github.io !

3:57, often appear the message "find: './containerd': Permission denied", this is because AM expects you install everything in /opt, to use a version that can work in any container or custom $HOME you want, use the portable version of AM, i.e. "AppMan", at https://github.com/ivan-hc/AppMan

I started writing AM/AppMan two years ago, it was just a custom script to install and always keep any Appimage package I needed updated to the latest version. Then become something much bigger.

AppMan, at https://github.com/ivan-hc/AppMan, a copy of "AM" but portable, it can install everything into a directory of your choice in your $HOME, no root privileges are required.

AppMan, a copy of AM but that allows you to choose where to install the apps in your HOME directory and without root access.

More details at https://github.com/ivan-hc/AppMan

https://github.com/ivan-hc/AM-AppMan ("AppMan", local integration only).

RELEASE: https://github.com/ivan-hc/AppMan/releases/tag/3.0.6.1

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.

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.

My project bread or AppMan by Ivan are basically package managers for AppImages, I use GitHub release & the Above given appimage.github.io API to get the information related to AppImages stored in this repository, and AppMan has it's own repository maintained by Ivan.

Bread 🍞: https://github.com/DEVLOPRR/bread