zap
AM
zap | AM | |
---|---|---|
17 | 76 | |
485 | 318 | |
- | - | |
4.1 | 9.9 | |
9 months ago | 6 days ago | |
Go | Shell | |
MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
zap
- Working on an app to "install" and manage AppImages
-
Why doesn't appimage have this?
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.
- Lamenting What AppImage Could Have Been
-
Install snap vs deb (ppa) for Ubuntu 22.04?
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.
- Zap: The delightful package manager for AppImages
-
appimage-builder 1.0.0 was released, a tool for packing applications along with all of its dependencies using the system package manager to obtain binaries and resolve dependencies.
That said, there is Zap.
-
Bread, It's History & Minor Patch v0.7.2
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.
-
Interesting Benchmarks of Flatpak vs. Snap vs. AppImage
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.
-
It's time to fork some good projects
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.
- AppImage and centralized repositories: my point of view
AM
-
How do you (yes, you specifically) work with appimages?
I recently discovered AM App Manager, it's app manager for appimages that have system integration and you can update all your apps with one command. Take a look at it's catalog to see if your app is supported.
-
Install issue on PopOS using appImage
I use https://github.com/ivan-hc/AM-Application-Manager to install App image, to include Neovim. By default it currently installs Version 10.0 and creates the symlinks.
-
I'm sick of reading that among the disadvantages of AppImage is the lack of updates and a centralized repository!
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 !
-
ArchImage: my (experimental) side-project to convert Arch Linux programs to AppImages that really work on any distro, old or young... powered by Junest
In conclusion, I feel really confortable with docker/podman/distrobox/junest... but I also like a lot AppImage packages, so I'm trying to merge both. Something I learned all this time I use Linux is that there is no distro, no package format, no software... that can really satisfy my needs. The best hing I can do to solve this situation is to built it by myself (this is my main project, I named it "AM"). I spent two years to create what I like, after a decade as a common Linux user that uses what distro/package mantainers had to give, and this make me feel better. This last point is the main reason because all these distros and software solutions exists in GNU/Linux.
-
Ventoy Installation
This is one of the 1700 installation scripts of my project.
-
After two years of development on "AM", AppMan and many Appimage packages... I'm seriously considering giving it all up
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.
-
I have developed my own Appimage package manager in full BASH, here are 3 different approuches to install the apps: xterm (1, the default one, allows to interact when prompted questions), less (2, clean but non interactive) or nothing (not clean). What is better? Have you got suggestions?
Sure https://github.com/ivan-hc/AM-Application-Manager I have already tried with lowercases words but I don't like that, that's why I've chosen uppercased text. "De gustibus non est disputandum", Romans said.
-
Portable Arch Linux packed into a single executable
I like containers, I've tried Junest and docker/podman/distrobox... also I work a lot with portable apps (see here) and I've also published a website for them (here) so I'm amazed on how you've built something that can merge them! I'll include it on my catalog (also I'm writing an installation script for it). Thank you!
- Portable-Linux-apps.github.io reached 1608 applications (about 1570 are Appimage packages), all with descriptions and links to the authors, sources... and installation scripts I wrote one by one.
-
After a long waiting and big cleaning of the code... "AM" Application Manager is back: 1596 installation scripts (i.e. about 1550 Appimage packages, all installable and updatable). And the uploading is not finished yet!
Learn more at https://portable-linux-apps.github.io
What are some alternatives?
AppImageUpdate - AppImageUpdate lets you update AppImages in a decentral way using information embedded in the AppImage itself.
firedragon-browser - A Floorp fork with custom branding 🐉 (mirrored from GitLab)
AppImageLauncher - Helper application for Linux distributions serving as a kind of "entry point" for running and integrating AppImages
AppMan - Manage 1900+ AppImage packages and official standalone apps for GNU/Linux without root privileges using the extensible and ever-growing AUR-inspired database of "AM Application Manager". Easy to use like APT and powerful like PacMan.
Spotify-appimage - Unofficial AppImage for Spotify
appimagepool - A simple, modern AppImageHub Client, powered by flutter.
gimp-appimage
gvm - Go Version Manager (gvm) enables seamless installing and swapping between Go versions with a single command. This tool manages a Go environment for the user by allowing a user to specify which Go version they wish to use and handling all of the steps to install and configure that Go version. GVM also supports installing Go from the official Golang master branch so that you can easily try the next version of Go without waiting for a pre release build.
GIMP-x86_64.AppImage - GNU Image Manipulation Program, cross-platform image and photo editor, AppImages for x86 and x64 architectures built from the more recent PPA (supports GLIBC 2.27 or later). [Moved to: https://github.com/ivan-hc/GIMP-64bit-and-32bit.AppImage]
GIMP-64bit-and-32bit.AppImage - GNU Image Manipulation Program, cross-platform image and photo editor, AppImages for x86 and x64 architectures built from the more recent PPA (supports GLIBC 2.27 or later). [Moved to: https://github.com/ivan-hc/GIMP-AppImage]
nyxt - Nyxt - the hacker's browser.