-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
ability to specify additional build dependency mirrors that affect any package in the full dependency tree #14292
Comments
Imho, this is a pretty important feature, especially in a company context. Consider the following scenario: ACME is depending on some external packages (clap and zig-ini) and set up a local caching server where all their dependencies must be stored for archiving reasons. This would require both an additional mirror ( Another option would be to give URLs a priority, so that Zig will prefer mirrors with higher priority first, and in this case, prefer the cache url over the others. |
As a user compiling software, I shouldn't have to modify the build.zon to add my local mirror. I should be able to provide some sort of overrides file (or potentially via argument/environment variable?) |
Good point! I guess it's better to not modify the project in order to add overrides |
thats a separate but valid use case. the developer should still be able to provide mirrors as well |
Extracted from #14265.
After supporting URL mirrors (#14291), an additional enhancement is to allow any project in the dependency tree to provide additional mirrors for any dependency in the entire tree.
This might look something like:
This would provide a way for a project to vendor dependencies in a git branch, or use something like git-subtrac.
The text was updated successfully, but these errors were encountered: