5 ms·
This is one of the reasons I like Guix so much: its packaging system treats source builds as the normal case, with binary packages available via caching. So if
by ryukafalz 1y ago
This is one of the reasons I like Guix so much: its packaging system treats source builds as the normal case, with binary packages available via caching. So if you go to install a package and there's no cached binary, Guix will happily build it for you on the spot, with bitwise reproducibility if it can. You still get the benefits of prebuilt packages, but you always have that escape hatch.
This also means that it's trivial to install a patched version of a package through the same package manager as everything else. No dedicated build infra required (though of course if you're deploying to a large fleet you may want to set up some build servers to avoid the need for rebuilds on most machines).
- hedora 1y agoDebian has been like this in practice for at least 25 years (when I first switched to it). The builds weren’t reproducible back then, but never mattered in practice for me personally. Now, the vast majority of the packages have reproducible builds, which is good enough for me. (Though these days I’m using devuan because I’ve never seen a stable systemd desktop/laptop that uses .debs)
- r14c 1y agoDebian isn't source transparent in the same way tho. (I'm mostly nitpicking). That said, the contributions that Debian has made in terms of reproducible builds can't be understated. They built a wonderful foundation for the likes of nix and guix to build on.
- Imustaskforhelp 1y agoIsn't nix for the most part same in that sense though compared to guix?
- ryukafalz 1y agoProbably! I just have more experience with Guix than Nix so I don't know what it feels like in practice on the latter.