Go dependency tool
Go Shell
Latest commit 8ac86c2 Feb 21, 2017 @mattn mattn committed with sdboyer remove needless generating files in test
Permalink
Failed to load latest commit information.
cmd/dep case-insensitive GOPATH Feb 21, 2017
hack add script to check if changes to vendor are valid Jan 19, 2017
test Fix tempdir path normalization in test Helper Feb 13, 2017
testdata Increasing coverage for lock and analyzer Feb 13, 2017
vendor/github.com Chase latest gps Feb 2, 2017
.gitattributes Prevent problems comparing golden files on Windows Feb 21, 2017
.gitignore Moving to want/got pattern and adding unit test coverage Feb 13, 2017
.travis.yml move command code into cmd subpackage Jan 28, 2017
AUTHORS Add repo boilerplate and readme Oct 7, 2016
CONTRIBUTING.md minor updates to contributing.md Jan 24, 2017
CONTRIBUTORS Add repo boilerplate and readme Oct 7, 2016
LICENSE Add repo boilerplate and readme Oct 7, 2016
PATENTS Add repo boilerplate and readme Oct 7, 2016
README.md Add note about required Go version to README Feb 8, 2017
analyzer.go Increasing coverage for lock and analyzer Feb 13, 2017
analyzer_test.go Remove TestAnalyzerInfo() per feedback Feb 13, 2017
appveyor.yml move command code into cmd subpackage Jan 28, 2017
context.go case-insensitive GOPATH Feb 21, 2017
context_test.go remove needless generating files in test Feb 21, 2017
fs.go refactored so there would be one IsNonEmptyDir check instead of an Is… Feb 11, 2017
fs_test.go Fix test issue after upstream merge Feb 13, 2017
lock.go Increasing coverage for lock and analyzer Feb 13, 2017
lock.json Update memo in lock Feb 2, 2017
lock_test.go Moving to want/got pattern and adding unit test coverage Feb 13, 2017
manifest.go move command code into cmd subpackage Jan 28, 2017
manifest.json Chase latest gps master Jan 4, 2017
manifest_test.go Moving to want/got pattern and adding unit test coverage Feb 13, 2017
project.go move command code into cmd subpackage Jan 28, 2017
project_test.go Adding -update test flag for golden files Feb 13, 2017
txn_writer.go move command code into cmd subpackage Jan 28, 2017
txn_writer_test.go Moving to want/got pattern and adding unit test coverage Feb 13, 2017

README.md

Dep

Linux: Build Status | Windows: Build status

Dep is a prototype dependency management tool. It requires Go 1.7 or newer to compile.

Dep is NOT an official tool. It is not (yet) blessed by the Go team.

It IS, however, the consensus effort of most of the Go community, and being integrated into the go toolchain is the goal.

We're working on a roadmap with more details.

Current status

Pre-alpha. Lots of functionality is knowingly missing or broken. The repository is open to solicit feedback and contributions from the community. Please see below for feedback and contribution guidelines.

Context

Usage

Get the tool via

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

Typical usage on a new repo might be

$ dep init
$ dep ensure -update

To update a dependency to a new version, you might run

$ dep ensure github.com/pkg/errors@^0.8.0

See the help text for much more detailed usage instructions.

Note that the manifest and lock file formats are not finalized, and will likely change before the tool is released. We make no compatibility guarantees for the time being. Please don't commit any code or files created with the tool.

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? Please check the existing issues to see if your feedback has already been reported. If not, please file 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.