this post was submitted on 14 Jun 2026
8 points (100.0% liked)
Programming
27417 readers
71 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Here is an explanation for that - I think it is valid for Debian, too:
https://wiki.archlinux.org/title/Guix
Where exactly in there?
You mean this? That would explain it.
Well, it has only 31,000 packages for now, and quite limited npm support ;-)
But more serious, the user interface is still being polished. The documentation is top notch though, including the parts how to define own packages!
What's also worth mentioning is that Guix packages are also an excellent way to distribute new FLOSS software for Linux/POSIX - your packages do not need to be part of the Guix distribution.
You can just put your package definition on your Codeberg or github page and users can pull that. Pretty much like Ubuntu PPAs or flatpaks but since everything is defined from source, people can inspect what they get, which fosters trust.
And it works for any distro that works with Guix, without modification, because the Guix dependencies give a 100% reproducible base.
No,I mean the first paragraph in section 1,"Installation", which is explaining clearly why it has no advantage to install it as a distribution package. Arch supports both ways, but installing Guix separately is recommended.