| author | |
| committer | |
| log | 77c63ac36034db577a9287c54fb6771429a7428f |
| tree | b18749386ae77c8dabcd1f96d42e6eb7bdc13b61 |
| parent | 0ff0bdb4a71d8fd055272abfdadea2f23f99574a |
There's been some proliferation of dependency URLs that reference
mutable data such as links to git branches that can change. This has
resulted in broken projects, i.e.
* https://github.com/RohanVashisht1234/raylib_rain_train/blob/9eef9de94c511f2eb4fe5db1d6abd574ee245c9b/build.zig.zon
* https://github.com/rcmagic/ZigFightingGame/commit/4b64353e9c69de0fa2eb87fa9c3a3da76a8a3e7b
There's also disagreement about whether it's fine for URL's to point to
git branches, i.e.
https://github.com/Not-Nik/raylib-zig/pull/130
This updates the docs to mention that zig won't be able to use URLs if
their content changes.2 files changed, 4 insertions(+), 2 deletions(-)
doc/build.zig.zon.md+2-1| ... | ... | @@ -47,7 +47,8 @@ String. |
| 47 | 47 | |
| 48 | 48 | When updating this field to a new URL, be sure to delete the corresponding |
| 49 | 49 | `hash`, otherwise you are communicating that you expect to find the old hash at |
| 50 | the new URL. | |
| 50 | the new URL. If the contents of a URL change this will result in a hash mismatch | |
| 51 | which will prevent zig from using it. | |
| 51 | 52 | |
| 52 | 53 | #### `hash` |
| 53 | 54 |
lib/init/build.zig.zon+2-1| ... | ... | @@ -27,7 +27,8 @@ |
| 27 | 27 | //.example = .{ |
| 28 | 28 | // // When updating this field to a new URL, be sure to delete the corresponding |
| 29 | 29 | // // `hash`, otherwise you are communicating that you expect to find the old hash at |
| 30 | // // the new URL. | |
| 30 | // // the new URL. If the contents of a URL change this will result in a hash mismatch | |
| 31 | // // which will prevent zig from using it. | |
| 31 | 32 | // .url = "https://example.com/foo.tar.gz", |
| 32 | 33 | // |
| 33 | 34 | // // This is computed from the file contents of the directory of files that is |