go-appimage VS nonguix

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.

Their software freedom policy seems to be similar to Debian. All free by default, allow separate nonfree addon. In the case of Guix you can find that here: https://gitlab.com/nonguix/nonguix .

The GUIX community has a non-free package repo, you just add it as a GUIX channel and problem solved:

https://gitlab.com/nonguix/nonguix

Yes, being a GNU project Guix has a strict free software only policy. The biggest channel (repo) with proprietary stuff for Guix is called nonguix. It has the vanilla kernel, Nvidia drivers and a number of other proprietary packages including Steam, Chrome and the like. I don't know what the state of ZFS on Guix is though as I don't care for it myself, but I can see why its inclusion would be questioned with regards to licensing.

Since Guix is a GNU project, it doesn't support proprietary software (Steam, Discord, Zoom...). Third-party repos are available for it.

There's a git lab repo for non-free/libre software that you can add as a channel when installing. I used the following guide that shows you how to do this.

I'm trying to enable substitues for nonguix. I added the code snippet from the nonguix website to my system.scm file per the instructions. When I try to reconfigure I get the following error: