I’m seeing a curious dependency fetch behaviour in 0.14.0 which must have slipped in as a last minute change (because I was following the 0.14.0-dev versions quite closely):
In the sokol-zig build.zig.zon I have a dependency on a git repo that’s not a Zig project (and doesn’t have a build.zig.zon):
…when I run zig build
multiple times, I can see that this dependency is fetched each time (or at least the build process is stuck on this each time for half a second or so).
In the global Zig cache there is only one entry though (so at least it’s not polluting the cache):
zig ➤ fd emsdk
p/N-V-__8AAOG3BQCJ9cn-N2swm2o5cLmDhmdHmtwNngOChK78/emsdk
p/N-V-__8AAOG3BQCJ9cn-N2swm2o5cLmDhmdHmtwNngOChK78/emsdk.bat
p/N-V-__8AAOG3BQCJ9cn-N2swm2o5cLmDhmdHmtwNngOChK78/emsdk.ps1
p/N-V-__8AAOG3BQCJ9cn-N2swm2o5cLmDhmdHmtwNngOChK78/emsdk.py
p/N-V-__8AAOG3BQCJ9cn-N2swm2o5cLmDhmdHmtwNngOChK78/emsdk_env.bat
p/N-V-__8AAOG3BQCJ9cn-N2swm2o5cLmDhmdHmtwNngOChK78/emsdk_env.csh
p/N-V-__8AAOG3BQCJ9cn-N2swm2o5cLmDhmdHmtwNngOChK78/emsdk_env.fish
p/N-V-__8AAOG3BQCJ9cn-N2swm2o5cLmDhmdHmtwNngOChK78/emsdk_env.ps1
p/N-V-__8AAOG3BQCJ9cn-N2swm2o5cLmDhmdHmtwNngOChK78/emsdk_env.sh
p/N-V-__8AAOG3BQCJ9cn-N2swm2o5cLmDhmdHmtwNngOChK78/emsdk_manifest.json
I assume this is a bug (maybe related to the new naming convention for cache entries), but first wanted to ask here if anybody else sees this behaviour before writing a ticket.
PS: to reproduce (this is on macOS):
git clone https://github.com/floooh/sokol-zig && cd sokol-zig
zig build
zig build
zig build
...
…the second and third time zig build is run you can see for a short moment that the emsdk dependency is fetched again.