-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
ability to fetch dependencies via subversion protocol #14296
Copy link
Copy link
Open
Labels
contributor friendlyThis issue is limited in scope and/or knowledge of Zig internals.This issue is limited in scope and/or knowledge of Zig internals.enhancementSolving this issue will likely involve adding new logic or components to the codebase.Solving this issue will likely involve adding new logic or components to the codebase.zig build systemstd.Build, the build runner, `zig build` subcommand, package managementstd.Build, the build runner, `zig build` subcommand, package management
Milestone
Metadata
Metadata
Assignees
Labels
contributor friendlyThis issue is limited in scope and/or knowledge of Zig internals.This issue is limited in scope and/or knowledge of Zig internals.enhancementSolving this issue will likely involve adding new logic or components to the codebase.Solving this issue will likely involve adding new logic or components to the codebase.zig build systemstd.Build, the build runner, `zig build` subcommand, package managementstd.Build, the build runner, `zig build` subcommand, package management
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
Status
Fetching
Extracted from #14265.
zig buildshould support fetching via an URL like this:Note that the fragment is used to fetch a particular commit. I suppose the fragment could be omitted, meaning to fetch the tip of trunk, however, this would be not advised since the hash would be wrong as soon as another commit is pushed to that branch. Ideally, if the fragment is omitted then an error would be emitted telling the user to add the fragment, giving them a copy+pasteable snippet, or perhaps even editing the manifest file on the user's behalf.
Whether this is built-in or ends up being closed and relying on a third-party to provide a fetch plugin (#14294) will be determined based on the complexity of implementing and maintaining the svn protocol.
I think the first step would be to implement this as a third-party fetch plugin, and then we can evaluate whether it can be upstreamed and become a builtin.
Related: