AppImageUpdate
pkg2appimage
AppImageUpdate | pkg2appimage | |
---|---|---|
21 | 14 | |
545 | 672 | |
1.1% | 0.9% | |
4.6 | 6.9 | |
6 months ago | 4 months ago | |
C++ | Shell | |
MIT License | MIT License |
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.
AppImageUpdate
- Why the neovim in the mint repo is so old? Im currently using mint 21.2. Is there a newer version available already? Im not able to use the plugins in this old version, and the snap version seems kinda laggy for me
- Why do I have do download >1 GB for Okular PDF viewer over flatpak? Installing it over dnf just totals to 81 MB
-
Appimages are too large, Flatpak is the way to go!
There's an updater for appimages https://github.com/AppImageCommunity/AppImageUpdate
-
Lamenting What AppImage Could Have Been
AppImages can contain update information (and even support partial updates using zsync), check out https://github.com/AppImage/AppImageUpdate.
-
App Manager For .AppImage File
https://github.com/AppImage/AppImageUpdate this only works if the application has information regarding where to fetch the update from...
-
feat: Linux AppImage update information
It would be very nice and handy if we could easily update Tutanota Linux desktop app. Luckily, since it is packaged as an AppImage, there's an easy-to-integrate utility available just for that.
-
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.
It's not centralised, not like Snap with SnapCraft, not even like Flatpak with it's 'not technically but kinda is in practice' Flathub repository. Anyone can make an AppImage, anyone can host an AppImage, anyone can download and run an AppImage, anyone can implement AppImage integration in a distro, and there's even a nice system for automatic updates for AppImage which again is nicely decentralised.
-
Interesting Benchmarks of Flatpak vs. Snap vs. AppImage
Some have built-in. some not. Btw I considered AppImageUpdate , but it would become re-install a full new app
-
AppImage and centralized repositories: my point of view
The fact is that the delta update system via Zsync and appimageupdatetool are real solutions to the problem, but too many developers do not implement it in their AppImage, myself included.
-
Installing an openSUSE desktop for a non-technical person
Btw, regarding Flatpak, I've had multiple issues related to mouse cursor, fonts, and local folder access - all related to the sandboxing of apps, all resolvable, but potentially a problem for a non-technical user. I've had much better experiences with AppImages, but I don't know if they have a graphical app store like interface; even the AppImageUpdate idea is still catching on.
pkg2appimage
-
If you are on debian you can use this trick to pack any package in deb repository as appimage with its deps!
The pkg2appimage script exists to do these conversions with many examples https://github.com/AppImageCommunity/pkg2appimage/tree/master/recipes
-
SimpleScreenRecorder, a screen recorder for Linux (X11) is now available as an (Unofficial) AppImage
NOTE: I've built it using the recipe available at https://github.com/AppImageCommunity/pkg2appimage, added libunionpreload from https://github.com/project-portable/libunionpreload and some additional paths to LD_LIBRARy_PATH into the AppRun, just tested on Debian and Arch Linux... and works great!
-
"AM" and AppMan - that's why they don't include support for AppImageHub and similar sites
Beyond all, my work is heavily focused on compiling AppImage from existing .deb packages through the use of pkg2appimage and appimagetool, as unofficial AppImage packages not present on AppImageHub are provided, but taken from fairly reliable sources ( Debian repositories, or in some cases a PPAs for Ubuntu). The sources are available via the -a or -w options of my scripts.
-
What's the deal with "snap vs flatpack" rivalry I seem to see around the internet?
Does anyone actually do that? The official documentation says not to do that (see here). Also, the excludelist mentions a couple of problems that happen when certain libraries are bundled in an AppImage.
-
Is it possible to have a Multi-Linux distro that has the main features of the rest?
It sounds like there might also be at least some support for portable Linux formats on Mac: snap appears to allow installing on mac via brew, but it sounds like appimages and flatpaks cannot run on mac. that said, i haven't used snaps on mac nor have I ever heard of anyone who does so... so no clue if they work well there.
-
For those interested in compiling an AppImage for Chromium...
PS: yes, I know that better sources for this are already available, for example the Slackware repository and woolyss, but actually the more recent version, the 97, for old i386 machines is provided by Debian (ArchLinux32 has the v90, and other versions are quite buggy for this architecture, see this issue). Unluckily there is not a 32 bit version of pkg2appimage, if we had one or someone can fork better the main script, we can still have more appimages for old architectures, being many of my scripts for x86_64 wrote to support pkg2appimage (as you have already seen in my previous post).
-
Issue in creating an AppImage for GIMP
If I have time enough, I wanna try to create a script that automatizes all the processes, also for you developers, but my knowledge is limited to the download of packages from Debian and derivatives or from Arch Linux to create these structures, I'm not much good in compiling these programs by myself into a chroot, I'm just an enthusiast.
-
Why doesn't everyone use appimages instead of .deb, .rpm or other native binary system?
Depends on who makes them, but generally everything besides this list
- aisap - Android-like sandboxing for AppImages
-
Any Appimages for linux?
Brave doesn't officially provide any AppImages. There is a issue on GitHub tracking this, but it's definitely not their top priority right now. You can use pkg2appimage to produce an AppImage of Brave or use existing ones available on this GitHub repository. Keep in mind that these are unofficial sources that I don't recommend to use, but if you really want to, at your own risk.
What are some alternatives?
AppImageLauncher - Helper application for Linux distributions serving as a kind of "entry point" for running and integrating AppImages
AppImageKit - Package desktop applications as AppImages that run on common Linux-based operating systems, such as RHEL, CentOS, openSUSE, SLED, Ubuntu, Fedora, debian and derivatives. Join #AppImage on irc.libera.chat
topgrade - Upgrade everything
deb2appimage - Build AppImages from deb packages on any distro with simple json configuration
zap - :zap: Delightful AppImage package manager
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
firejail - Linux namespaces and seccomp-bpf sandbox
flathub - Issue tracker and new submissions
winsparkle - App update framework for Windows, inspired by Sparkle for macOS
com.skype.Client
linuxdeployqt - Makes Linux applications self-contained by copying in the libraries and plugins that the application uses, and optionally generates an AppImage. Can be used for Qt and other applications
ostree - Operating system and container binary deployment and upgrades