-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
introduce the zig fetch
subcommand and symlink support in zig packages
#17363
Conversation
cc @ianprime0509 - would you be willing to add the git.zig logic to add symlink support here? |
Awesome! Sure, I'll take a closer look at this after work and send a patch to add support for this in Git. |
There are no functional changes in this commit.
zig fetch [options] <url> zig fetch [options] <path> Fetches a package which is found at <url> or <path> into the global cache directory, printing the package hash to stdout. Closes #16972 Related to #14280 Additionally, this commit: * Adds uncompressed .tar support to package fetching * Introduces symlink support to package fetching
* Package: use std.tar diagnostics to give detailed error messages * std.tar: add diagnostic for unsupported file type
eagerly awaiting @vesim987's upcoming PR for this |
Note that |
@andrewrk not sure what would be most convenient for you (maybe I should just send a follow-up PR once this is merged), but here's a patch to integrate this with This is able to fetch the dependency in this PR: kristoff-it/orca-ui-hello-zig#1
Sample when the underlying filesystem doesn't support symlinks:
|
If you're fine with it, I can cherry-pick from your zig fork into this branch |
That sounds like an easier idea, I just pushed it up here: https://github.com/ianprime0509/zig/tree/tar-symlinks |
Commit looks great 👍 |
Fetches a package which is found at
<url>
or<path>
into the global cache directory, printing the package hash to stdout.Closes #16972
Related to #14280
Additionally, this branch:
Merge Checklist
more kinds of symlink metadata in std.tareagerly awaiting @vesim987's upcoming PR for this