When I think of deterministic builds, I think of the ROMs on the old GameBoy. Apparently some of the ROMs had whatever empty space was left in the fixed-size image padded with random data pulled straight out of the build host's memory. As if consistent tool versions weren't already enough of a challenge!
Comments
When I think of deterministic builds, I think of the ROMs on the old GameBoy. Apparently some of the ROMs had whatever empty space was left in the fixed-size image padded with random data pulled straight out of the build host's memory. As if consistent tool versions weren't already enough of a challenge!
Just in case someone (like me) is not familiar with the concept of deterministic builds, this is a good read:
https://blog.torproject.org/blog/deterministic-builds-part-o...
Synopsis:
"deterministic builds" -- packages which are byte-for-byte identical no matter who actually builds them, or what hardware they use.
Isnt nix and guix a kind of solution that the deterministic build problem?
They produce builds with hashes of the source and all dependencies and tools used, or so I believe after skimming their manuals.
They're not really a solution if the official binaries are compiled using VC, and you want to compare to that.