Clone this repo:
  1. 87f3094 Update README to clarify project status by sam boyer · 6 weeks ago master
  2. ac31146 README: clarify current status of Go dependency management by Alberto Donizetti · 4 months ago
  3. 5600de0 Merge pull request #2196 from anthonyfok/patch-1 by Sunny · 10 months ago
  4. 2cdb640 Fix minor typo (caught by Lintian) by Anthony Fok · 10 months ago
  5. 1f7c19e CHANGELOG: prepare for 0.5.4 release by Kevin Burke · 12 months ago v0.5.4

Would you like to see your company name here? We're looking for a stable source of funding.

Dep

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

dep was initially developed to experiment with a new dependency management system for Go; but, as of Go 1.11, the Go project has officially adopted a different approach, based on the concept of Modules, which is described in a series of posts published on blog.golang.org.

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

Installation

You should use an officially 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 Debian platforms you can install or upgrade to the latest version with apt-get:

$ sudo apt-get install go-dep

On Windows, you can download a tarball from go.equinox.io.

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 getting the source code, or 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.