Interesting, I’ve been porting nixos to the nano pi m4 v2, this looks quite a bit less painful in some ways. Added to my: try this out some day list of stuff to look at.
Conceptually speaking, Guix got a lot of things right. On the other hand, Nix precedes Guix, the opposite would have been concerning.
The documentation is amazing, they are very careful about their tooling vendor lock-in. Their clean API around the toolchains and the abstractions around derivations is the selling point to me. The language is also somehow standard and comes full batteries included tooling-wise.
There’s a catch however: the Guix packageset is much smaller, you won’t have all the nice language-specific build systems you have with Nix, overall you’re likely to miss some stuff packaging-wise. Also: no systemd (I guess it might be a selling point for some people though).
Yep yep, this just intrigued me as I’ve gotten a bit deep in the guts of how nixos sd images are built. Its honestly not too big of a deal its just probably in need of a bit of a refactor tbh for the overall function to do this stuff but it honestly just strikes me as more: this was evolved not planned. Which is fine, just not as polished as it could be.
The scheme bit made a lot more sense to me off the bat versus having to do a fair amount of digging to figure out how I can adjust the partition sizes and make sure that my custom u-boot and its spl files etc… are getting put in the “blessed” right spot for this board (still not sure i am doing it right tbh as its not booting).
And the systemd bit is water under the bridge to me, that ship has sailed. I’ve had to port/add custom derivations to nixpkgs a lot so i’m not too averse to that if needed.
My real reason for all this is i’m building a little k8s cluster out of arm boards for shits, so nixops is my ultimate goal here.