-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
zig fetch -h should include examples #20096
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
Comments
Why was this issue closed as not planned? Is it tracked else where? I hit a case that the zig package is a subpath of the repo/tarball (here). And the build depends on another subpath to build the C lib. Some document on zig fetch and the format of build.zig.zon file would be helpful .. This page seems helpful to specify an alternative path to resolve the root path. But nothing about how zig fetch can work. (What kind of URL it expects.) |
Any chance of reconsidering this issue? I just hit the same thing, and I couldn't figure out from the help output what URL I'm supposed to pass to This also is one of the top results when I search zig fetch --save https://github.com/JacobCrabill/zigdown/archive/refs/heads/main.tar.gz |
No, zig will not endorse one version control system over another, nor one code hosting service over another, by including examples of them. |
It doesn't even have to be a real vendor. This would be fine:
Possibly in addition, are you open to more specificity in the help output to let the user know that the URL is supposed to be to a source tarball? Because currently the help text just says "url" without specifying what kind of URL it should be. |
Sure, that sounds like a nice enhancement 👍 Feel free to submit a patch. |
The current zig fetch help docs tell the user to specify a package's URL, but it's unclear what the URL should be. This change expands the help output to explain what URLs the zig fetch command can handle and provides examples of valid URLs. Related: ziglang#20096
The current zig fetch help docs tell the user to specify a package's URL, but it's unclear what the URL should be. This change expands the help output to explain what URLs the zig fetch command can handle and provides examples of valid URLs. Related: ziglang#20096
The current zig fetch help docs tell the user to specify a package's URL, but it's unclear what the URL should be. This change expands the help output to explain what URLs the zig fetch command can handle and provides examples of valid URLs. Related: ziglang#20096
The current zig fetch help docs tell the user to specify a package's URL, but it's unclear what the URL should be. This change expands the help output to explain what URLs the zig fetch command can handle and provides examples of valid URLs. Related: #20096 A git bundle file seems to be the more accurate term, as it's what git uses in its documentation: https://git-scm.com/docs/git-bundle
Uh oh!
There was an error while loading. Please reload this page.
zig fetch -h
orzig fetch --help
currently tells us:But should ideally provide examples:
Which formats are supported? Tar and more recently Zip (I believe gzipped Tar is also supported?)
But then there's git URLs, which I believe are supported. Maybe I'm the only one who doesn't know enough about Git but my naïve attempts are not working.
After trying a bunch of things I realized I made some dumb mistakes like doing
git fetch
instead ofzig fetch
sometimes or doingzig fetch
with a plainhttps
schema instead of agit+https
schema. I've removed the specifics which are not really useful.So I'm assuming an example will help others besides me. (And perhaps there are multiple kinds of Git URLs that work?)
The text was updated successfully, but these errors were encountered: