Clone this repo:
  1. 22125cf cmd/dep: replace `len(x)<=0` with `len(x)==0` (#2031) by Iskander (Alex) Sharipov · 7 weeks ago master
  2. 3c04147 Merge pull request #2002 from sdboyer/noverify-preserve-files by sam boyer · 2 months ago
  3. 8a9bd79 dep: Add test of noverify's preservation behavior by sam boyer · 2 months ago
  4. e32ec54 docs: Update noverify info about path preservation by sam boyer · 2 months ago
  5. 3807092 dep: Relative paths in shasum release files by sam boyer · 2 months ago

Dep

dep is a dependency management tool for Go. It requires Go 1.9 or newer to compile.

dep was the “official experiment.” The Go toolchain, as of 1.11, has (experimentally) adopted an approach that sharply diverges from dep. As a result, we are continuing development of dep, but gearing work primarily towards the development of an alternative prototype for versioning behavior in the toolchain.

For guides and reference materials about dep, see the documentation.

Installation

It is strongly recommended that you use a released version. Release binaries are available on the releases page.

On MacOS you can install or upgrade to the latest released version with Homebrew:

$ brew install dep
$ brew upgrade dep

On other platforms you can use the install.sh script:

$ curl https://raw.githubusercontent.com/golang/dep/master/install.sh | sh

It will install into your $GOPATH/bin directory by default or any other directory you specify using the INSTALL_DIRECTORY environment variable.

If your platform is not supported, you‘ll need to build it manually or let the team know and we’ll consider adding your platform to the release builds.

If you're interested in hacking on dep, you can install via go get:

go get -u github.com/golang/dep/cmd/dep

Feedback

Feedback is greatly appreciated. At this stage, the maintainers are most interested in feedback centered on the user experience (UX) of the tool. Do you have workflows that the tool supports well, or doesn't support at all? Do any of the commands have surprising effects, output, or results? Let us know by filing an issue, describing what you did or wanted to do, what you expected to happen, and what actually happened.

Contributing

Contributions are greatly appreciated. The maintainers actively manage the issues list, and try to highlight issues suitable for newcomers. The project follows the typical GitHub pull request model. See CONTRIBUTING.md for more details. Before starting any work, please either comment on an existing issue, or file a new one.