bf147cffb1
|
||
|---|---|---|
| .github | ||
| cmd/dep | ||
| docs | ||
| gps | ||
| hack | ||
| internal | ||
| testdata | ||
| vendor | ||
| website | ||
| .codeclimate.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .travis.yml | ||
| AUTHORS | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| CONTRIBUTORS | ||
| Gopkg.lock | ||
| Gopkg.toml | ||
| LICENSE | ||
| MAINTAINERS.md | ||
| Makefile | ||
| PATENTS | ||
| README.md | ||
| analyzer.go | ||
| analyzer_notwindows_test.go | ||
| analyzer_test.go | ||
| analyzer_windows_test.go | ||
| appveyor.yml | ||
| context.go | ||
| context_test.go | ||
| doc.go | ||
| install.sh | ||
| lock.go | ||
| lock_test.go | ||
| manifest.go | ||
| manifest_test.go | ||
| project.go | ||
| project_test.go | ||
| test_project_context_test.go | ||
| txn_writer.go | ||
| txn_writer_test.go | ||
README.md
Dep
dep is a prototype dependency management tool for Go. It requires Go 1.9 or newer to compile. dep is safe for production use.
dep is the official experiment, but not yet the official tool. Check out the Roadmap for more on what this means!
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.