David Wilson gives his tips, tricks and workflows for Guix system crafting. David is the creator of systemcrafters.net where he streams and creates content on Guix, Guile, Emacs and crafting the perfect Linux system.
Recording (edited) of the Guix London Meetup chat with Ludovic Courtès. Ludo is a long-term #FreeSoftware hacker, interested in #lisp, #scheme and #guile. He is excited by the #nix deployment model, and created #guix.
The sidetrack we took in the past started to give us some good news. Here there are some.
Introducing functions and modules in Guile Scheme and Guix
Now and then I find myself having to open a file or an application that I don't fully trust. A common technique to deal with this is to create a disposable environment (for example a so-called container or a virtual machine) where the file or application can be safely opened. Once used, the environment can be discarded.
Guix package structure: build-system overview build arguments
With the release of Libntlm version 1.8 the release tarball can be reproduced on several distributions. We also publish a signed minimal source-only tarball, produced by git-archive which is the same format used by Savannah, Codeberg, GitLab, GitHub and others. Reproducibility of both tarballs are tested continuously for regressions on GitLab through a CI/CD pipeline. If that wasn’t enough to excite you, the Debian packages of Libntlm are now built from the reproducible minimal source-only tarball. The resulting binaries are reproducible on several architectures.
We built GCC 4.6.4 with RISC-V support and C++ and all that and we made it run in Guix, finally.
We’ve got sidetracked, but it doesn’t really matter if we continue forward.
Guix package structure: inputs, native-inputs and propagated-inputs