e565a9f91e
* Always write the manifest when provided. * Write the lock only when modified or when writing vendor/. * Clarify what should be passed for the two locks args: old lock and new lock. Updated `dep init` to match this expectation. * Add test case for writing a new lock |
||
|---|---|---|
| cmd/dep | ||
| hack | ||
| test | ||
| testdata | ||
| vendor/github.com | ||
| .gitattributes | ||
| .gitignore | ||
| .travis.yml | ||
| AUTHORS | ||
| CONTRIBUTING.md | ||
| CONTRIBUTORS | ||
| LICENSE | ||
| PATENTS | ||
| README.md | ||
| analyzer.go | ||
| analyzer_test.go | ||
| appveyor.yml | ||
| context.go | ||
| context_test.go | ||
| fs.go | ||
| fs_test.go | ||
| lock.go | ||
| lock.json | ||
| lock_test.go | ||
| manifest.go | ||
| manifest.json | ||
| manifest_test.go | ||
| project.go | ||
| project_test.go | ||
| test_project_context_test.go | ||
| txn_writer.go | ||
| txn_writer_test.go | ||
README.md
Dep
Linux: 
| Windows:
Dep is a prototype dependency management tool. It requires Go 1.7 or newer to compile.
dep is NOT an official tool. Yet. Check out the Roadmap!
Current status
Alpha. Functionality is known to be broken, missing or incomplete. Command and file format changes are still planned. The repository is open to solicit feedback and contributions from the community. Please see below for feedback and contribution guidelines.
Context
- The Saga of Go Dependency Management
- Official Google Docs
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.