legacy packages are unnecessarily fetched

[blogscot]

Since I upgraded to to Zig 0.14.0 each time I build my local project the the raylib packages are being refetched 😭. If I'm not mistaken this is due to the new hash format. Apparently, the solution is to regenerate the hash values for C packages that do not contain build.zig.zon files. See links for further details:

Build.zig.zon: ‘raw’ dependencies are fetched on each build
legacy packages are unnecessarily fetched

[Not-Nik]

raylib does have a Zig build system integration, but hasn't updated their build.zig.zon, so this is an issue on their end. Please raise this in the main repo.

[silviogames]

The hashes have been updates in raylib it seems in this commit:
raysan5/raylib@bbeade6

I'm not very familiar with git and zig dependencies and was wondering as my project still fetches on every build and I'm using the most recent commit of this repository, what has to happen for the raylib commits to be added and fixing the fetch on every build in my project?

[Not-Nik]

Done!

[silviogames]

thanks!
so just for my understanding, you decide which commit of raylib you are using for you bindings by specifying the hash

[Not-Nik]

Yup, it's usually a release, but when we get a breaking Zig release like 0.14 I sometimes update to -dev versions.