Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 11
    @secmask go get is designed as a tool for the common case. The Go team explicitly decided against adding configurability so people adhere to standards instead of rolling out their own cruft. It was never made for the case you have (i.e. private repositories). Commented Dec 16, 2014 at 11:27
  • 1
    This is an interesting perspective, but the big limitation of this approach is the handling of recursive, private dependencies. Handling this in a scalable way would essentially require re-implementing go get, if SSH access couldn't be handled as described in other answers. Commented Mar 1, 2023 at 12:09
  • 1
    "manually put the repository in the right place" isn't a solution in a Go modules world. Commented Jun 28, 2024 at 13:57
  • @dolmen Correct. This answer predates Go modules. Commented Jun 28, 2024 at 15:48