Go dependency management tool experiment (deprecated)
Перейти к файлу
Tom Wilkie 2c84fee0cb Add dep prune subcommand
- Check the external dependencies match those in the lock file.
- Read all the dependencies out of the lock file, don't calculate them myself.
- Prune by rebuilding the vendor dir with WriteDepTree
2017-04-07 10:58:49 +01:00
cmd/dep Add dep prune subcommand 2017-04-07 10:58:49 +01:00
hack hack: update repo name 2017-02-21 20:15:57 -05:00
test Merge pull request #314 from tro3/harness_json_update 2017-03-14 21:41:12 -04:00
testdata Merge pull request #325 from carolynvs/fix-ensure-unmodified-lock 2017-03-20 12:12:57 -04:00
vendor/github.com Update gps to v0.15.0 2017-03-31 15:42:55 -04:00
.gitattributes Prevent problems comparing golden files on Windows 2017-02-20 23:45:11 -05:00
.gitignore Moving to want/got pattern and adding unit test coverage 2017-02-12 23:52:17 -05:00
.travis.yml Use patch wildcards in travis; re-add OSX 2017-03-31 21:26:15 -04:00
AUTHORS Add repo boilerplate and readme 2016-10-07 11:28:24 +11:00
CONTRIBUTING.md Update README, CONTRIBUTING with roadmap 2017-03-07 06:22:36 -05:00
CONTRIBUTORS Add repo boilerplate and readme 2016-10-07 11:28:24 +11:00
LICENSE Add repo boilerplate and readme 2016-10-07 11:28:24 +11:00
PATENTS Add repo boilerplate and readme 2016-10-07 11:28:24 +11:00
README.md Update README, CONTRIBUTING with roadmap 2017-03-07 06:22:36 -05:00
analyzer.go Update gps to v0.15.0 2017-03-31 15:42:55 -04:00
analyzer_test.go Remove TestAnalyzerInfo() per feedback 2017-02-12 23:52:17 -05:00
appveyor.yml Add 1.8 support for travis / appveyor 2017-02-23 12:45:59 -05:00
context.go Swap fmt.Errorf with errors.Errorf 2017-03-22 11:07:48 -05:00
context_test.go remove needless generating files in test 2017-02-21 01:19:15 -05:00
fs.go Wrap fs errors to include a better message and callstack 2017-03-09 13:05:30 -06:00
fs_test.go Fix test issue after upstream merge 2017-02-12 23:52:17 -05:00
lock.go Swap fmt.Errorf with errors.Errorf 2017-03-22 11:07:48 -05:00
lock.json Bump gps constraint 2017-04-01 21:23:41 -04:00
lock_test.go Don't leave open test file handles open 2017-03-09 13:28:46 -06:00
manifest.go Swap fmt.Errorf with errors.Errorf 2017-03-22 11:07:48 -05:00
manifest.json Bump gps constraint 2017-04-01 21:23:41 -04:00
manifest_test.go Don't leave open test file handles open 2017-03-09 13:28:46 -06:00
project.go Swap fmt.Errorf with errors.Errorf 2017-03-22 11:07:48 -05:00
project_test.go Adding -update test flag for golden files 2017-02-12 23:52:17 -05:00
test_project_context_test.go Wrap error so the test prints the stack trace 2017-03-21 15:14:08 -05:00
txn_writer.go Add dep prune subcommand 2017-04-07 10:58:49 +01:00
txn_writer_test.go Further simplify ensure payload logic 2017-03-19 11:47:09 -05:00

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. 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

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.