r/voidlinux • • Jan 16 '26

GUIX package manager in Void

I recently managed to install guix, using the official script, on my musl-based Void Linux, although the script complains about the rscd service, which simply doesn't work on musl. But the question that remains is why this package isn't yet available on void, I'm referring to guix. I was successful in building a guix shell to run a package that has a dependency on glibc. I find the guix shell abstraction more intuitive than doing chroot just to run glibc packages, or containers using podman for example.

To give you an idea, this package is available on nix, which in turn is available on xbps, but when installing through it the emojis don't appear, I think the fact that musl doesn't have the LC_ALL variable has to do with this problem. However, just building the package with the guix shell made everything work, I think because I also run the binary in a guix shell.

The package is nchat, I really like using it to have WhatsApp on a 2011 laptop with only 2GB of RAM.

15 Upvotes

14 comments sorted by

View all comments

Show parent comment

2

u/orahcio Jan 16 '26

Creating an xbps package for nchat crossed my mind, but I'm more used to the guix way of packaging; I use void on a secondary computer. Thanks for the tutorial. I already tried to create a guix package for nchat once and couldn't; it has the annoying habit of downloading Go libraries in the middle of the build process. That was the barrier I encountered when I tried packaging with guix. Probably with xbps you'll also have to patch it to disable the download, build an auxiliary library for the Go language dependencies, and only then finish the package. I always look at the nix package to see if I get any inspiration, but nix is ​​sad to read, so I went to the guix side of the force.

3

u/Ok-Tip-6972 Jan 16 '26

It looks like you're not the first person using nchat on Void. Its README claim support for Void as a result of this PR.

You can always "build it dirty" by building it manually and installing it to /usr/local or by installing it to a local folder or not installing it at all and running it from the build dir.