AppMan VS pkg2appimage

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

The pkg2appimage script exists to do these conversions with many examples https://github.com/AppImageCommunity/pkg2appimage/tree/master/recipes

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!

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.

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.

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.

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).

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.

Depends on who makes them, but generally everything besides this list

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.