Install GUIX on Macbook 12
I have an old Intel macbook 12 of begin 2016, one of the so-called "Retina Macbooks". It is an ideal couch device but far too slow to run modern OS-X, provided you wanted to run that to begin with.
I have an old Intel macbook 12 of begin 2016, one of the so-called "Retina Macbooks". It is an ideal couch device but far too slow to run modern OS-X, provided you wanted to run that to begin with.
I always spend too much time setting up a new project and thinking how to structure it. I decided to summuraize my experience, to enhance it with a small research and to write down my thoughts on the topic. So I can come back to it myself or reference in the discussion.
Fifteen months have passed since our last Guix/Hurd on a Thinkpad X60 post and a lot has happened with respect to the Hurd.
Fifteen months have passed since our last Guix/Hurd on a Thinkpad X60 post and a lot has happened with respect to the Hurd . And most of you will have guessed, unless you skipped the title of this post, the rumored x86_64 support has landed in Guix! Here is a not-so-short overview of our Hurd work over the past 1.5 years: The build daemon fails when invoking guix authenticate on the Hurd bug was fixed. This was our most pressing problem as it meant that we could not keep…
A cool thing about Guix (and probably functional package managers in general) is, that derivations form a directed acyclic graph, which means that all packages with their dependencies or system configurations can be represented as such. Another, even cooler, thing is, that Guix provides a graphing utility called `guix graph` which helps visualising these DAGs in Graphviz (if you ever wanted to frame a picture of your favorite package graph or play a game of "is this the dependency graph of a rust package or the visualization of a Mandelbrot set?" this should be the tool of your choice).
I've raised a few PRs against the Guix Codeberg repository recently, and each time I've done so with Forgejo's AGit workflow. This workflow is pretty nice, and allows me to raise a PR entirely from within Emacs. To do that, I've been using this code in my Emacs config to add an extra option to the magit-push transient to use the AGit flow to push to the upstream branch:
An update on the fundraising campaign to Sustain and Strengthen GNU Guix. Covers the fundraising done during the last few months of 2025 and into 2026. Goes into the proposed budget and activities for Guix Foundation during 2026. All the programmes are at a proposal stage, when this video was recorded, and may change depending on the decisions of the Foundation's membership council (SAC).
Results from Guix Fundraising We're on course to beat our fundraising target to sustain and strength Guix. We're bringing the fundraising campaign to an end, so let's cover how much we've raised and what it means for GNU Guix. After four months of fundraising we've raised €11,378 for the GNU Guix project. This means we've received money for 75% of our €15,000 annual goal. We also pre-registered tickets for Guix Days this year. Pjotr Prins and Manolis Ragkousis have done a stellar job organising it…
I've been meaning to write up a post on how I manage my Guix System configurations for a while, because I've hit on a solution that feels kinda nice, inspired by how folks do things in NixOS.
Recently I've been trying to get a PR merged with some fixes for Lua. I thought this would be a pretty straightforward thing to merge, but it turns out that modifying the Lua packages leads to 990 packages needing to be rebuilt. This is more than the 300 limit for a merge to master, so instead of merging my changes directly Andreas has kindly pushed them to a lua-team branch and queued it up behind go-team, gnome-team, and rust-team.