Re:Nix Survival Mode: macOS upgrades won't break Nix anymore
by tgamblin on Friday October 27, 2023 @09:59AM
(#38038501)
In Spack we rewrite strings in binaries, strings in text files (including shebangs), and RPATH/RUNPATH values. It's not hard to find store prefixes in binaries -- they have hashes in them so they're easy to identify. It's hard to lengthen them -- things in text files and in ELF fields can be made longer, but to make strings longer you need to find all references to them, which is impractical. So we build with long paths.
Relocating is really only a matter of relocating prefixes.
I am not sure how it would affect a content-addressed nix store, but I'm also not 100% sure why you want a content-addressed nix store. Addressing by the derivation hash (which is also what Spack does) lets you find valid build substitutes... would you index that separately for a content-addressed store?
Is the goal to allow multiple versions of non-reproducible builds in the same store?
Re:Nix Survival Mode: macOS upgrades won't break Nix anymore
by JamesSwift on Friday October 27, 2023 @05:20PM
(#38044117)
I'm not 100% sure, but I know one benefit of content-addressed derivations is that they are secure by default. i.e. if the hash matches the build is trusted vs the traditional need to have separate "trusted signatures" and signing workflow to whitelist particular builders.
Re:Nix Survival Mode: macOS upgrades won't break Nix anymore
by Nullabillity on Monday October 30, 2023 @09:02AM
(#38068969)
How do you reliably modify length-prefixed strings? Terminated strings? Delimited strings? Partial strings? Checksummed strings?
EDIT: theres also work being done to move to content-addressed nix store, in which case changing these things would invalidate the content hash