John Curve
Andrew KelleyIf you have a Zig project with dependencies, two big changes just landed which I think you will be interested to learn about.
Mitchell Hashimoto@andrewrk Big, both big. Mirroring is Ghostty's biggest problem (we want a way to mirror our full transitive list of deps w/ the same hash), followed by fetch retries.
@andrewrk I have this Nu script for our directs, but we can't do transitive ones: https://github.com/ghostty-org/ghostty/blob/6c0e02d1138d5376e4ac2f5e311b225494514a97/nix/build-support/update-mirror.nu
Qasim Shaikh@mitchellh based nushell user
Wolf480pl@andrewrk
so if I archive a project with its zig-pkg directory and the zig binary used to build it, that should be enough to rebuild that project 20 years later on a much newer system, as long as Linux kernel doesn't break its ABI?
so if I archive a project with its zig-pkg directory and the zig binary used to build it, that should be enough to rebuild that project 20 years later on a much newer system, as long as Linux kernel doesn't break its ABI?
@wolf480pl that's correct
ck@wolf480pl @andrewrk And with that in mind, why do you recommend not commiting the zig-pkg dir to version control? I'd see a lot of good properties there, like actually reviewable dependency updates.
Richard Levitte@ck @wolf480pl @andrewrk
It seems like the blog implies that zig-pkg could be stored and replicated separately. I'm frankly not sure that it needs being version controlled specifically, even.
It seems like the blog implies that zig-pkg could be stored and replicated separately. I'm frankly not sure that it needs being version controlled specifically, even.