pkg2appimage
bread
pkg2appimage | bread | |
---|---|---|
14 | 10 | |
669 | 32 | |
0.4% | - | |
6.9 | 0.0 | |
3 months ago | 27 days ago | |
Shell | Go | |
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.
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.
bread
-
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.
-
"AM" and AppMan - that's why they don't include support for AppImageHub and similar sites
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.
-
Idea for Appimages: AppImage Repositories! (Automatic Updates, Secure Downloads)
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 v0.4.4 released
- You can learn better while practicing, it took that to another level (I am intermediate in go),
- Install, Update, Remove & Run AppImages From CLI
-
Install, update, remove & run appimages from CLI
Bread 🍞: https://github.com/DEVLOPRR/bread
- Bread 🍞
- Go - A Simple Tool To Install, update and remove AppImage from your CLI
What are some alternatives?
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
appimage-cli-tool - AppImage package manager
deb2appimage - Build AppImages from deb packages on any distro with simple json configuration
go-appimage - Go implementation of AppImage tools
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
zap - :zap: Delightful AppImage package manager
flathub - Issue tracker and new submissions
lust - A fast, auto-optimizing image server designed for high throughput and caching; Now that is hot.
com.skype.Client
AM - An "AUR-inspired" Database of AppImage packages and a CLI to manage/install/update them system-wide! This repo lists 1900+ standalone apps for GNU/Linux. You can extend it with custom repositories, create your own installation scripts and even build AppImages on the fly! "AM" Application Manager: Easy to use like APT and Powerful like PacMan!
ostree - Operating system and container binary deployment and upgrades
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.