appimaged VS go-appimage

I can't speak for others but I use appimaged still, which monitors the ~/.local/bin directory and automatically adds the shortcut to my application menu in Ubuntu-Mate.

I found out that there is a daemon for it ([appimaged](https://github.com/AppImage/appimaged)) but it doesn´t seem to be supported anymore. The site points to an [alternative codebase](https://github.com/probonopd/go-appimage) but it is not clear (at least to me) if it is stable or not.

Hi u/tnc68, I use AppImageLauncher on Ubuntu to handle this automatically as it will handle the installation of new updates and preserve/generate desktop app icons for each update. Some users may prefer appimaged (as u/ProgsRS mentioned), but I currently do not use it.

There seem to be more than one solution to integrate AppImage with the desktop and still somehow a work in progress. The original version of appimaged is deprecated for a newer version written in go. There is also AppImageLauncher, which is not entirely the same as appimaged, but maybe does what you need. Docs: https://docs.appimage.org/user-guide/run-appimages.html#integrating-appimages-into-the-desktop

Snap and flatpak run a daemon to integrate into your system. Appimage has an optional daemon to give you the same integration https://github.com/probonopd/go-appimage

Handles making it executable, automatic upgrades, no need to move it to your $PATH, and adds the application to your app list.

Only other thing you might want to do is symlink a friendly name for cli

It's possible to make appimages that bundle a libc, although most don't. The go-appimage project contains a static build tool that will bundle the linker and wrap executable invocation in that. The intention seems to be providing support on older systems for programs built with a glibc that is too new, but I'm using it to ship a musl binary that can run on glibc systems.

I look forward to watching the FOSDEM talk this weekend, so perhaps getting ahead of myself. But I'm curious whether you think the move in appimage toward static linking would solve some of the hairy issues you pointed out? For example: https://github.com/AppImage/AppImageKit/issues/1193 and https://github.com/probonopd/go-appimage/

AppImage This seems like a convenient way of keeping Wine isolated from rest of the system. However, the documentation is still in research phase for this: https://github.com/AppImage/AppImageKit/wiki/Bundling-Windows-applications https://github.com/probonopd/go-appimage https://github.com/TheAssassin/AppImageLauncher https://github.com/sudo-give-me-coffee/wine32-deploy

There's an automatic way to make .desktop entries from appimage, I use https://github.com/probonopd/go-appimage/blob/master/src/appimaged/README.md

There are helper programs to help you manage them and integrate them with the system like other package formats.

their is you can use appimaged https://github.com/probonopd/go-appimage

Would be great if most distros (including Ubuntu, Fedora, etc.) would include AppImageLauncher or appimaged by default. Would make it much simpler for most people.