Go dependency management tool experiment (deprecated)
Перейти к файлу
Jonathan Stacks 5af30944ef
Add some logging to dep prune
2017-05-25 19:46:46 -05:00
cmd/dep Add some logging to dep prune 2017-05-25 19:46:46 -05:00
hack Fixed validate-vendor.bash to work with current dep implementation. 2017-05-25 13:18:26 +03:00
internal internal/fs: wrap CopyDir and copyFile errors 2017-05-26 01:38:57 +03:00
testdata Merge remote-tracking branch 'upstream/master' into add-metadata-to-sample-Gopkg-toml 2017-05-25 16:55:29 +03:00
vendor/github.com dep ensure 2017-05-25 14:36:24 +03:00
.codeclimate.yml adjust codeclimate exclude path 2017-05-10 14:18:34 +10: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 Remove staticcheck exemption 2017-05-11 00:28:51 -07:00
AUTHORS Add repo boilerplate and readme 2016-10-07 11:28:24 +11:00
CODE_OF_CONDUCT.md (To Squash) Moving CODE_OF_CONDUCT.md ../ 2017-04-25 09:11:55 -06:00
CONTRIBUTING.md Add a FAQ 2017-04-19 14:03:49 -05:00
CONTRIBUTORS Add repo boilerplate and readme 2016-10-07 11:28:24 +11:00
FAQ.md Spruce up symbolic links a bit 2017-05-23 21:28:05 -04:00
Gopkg.lock dep ensure 2017-05-25 14:36:24 +03:00
Gopkg.toml Bump to ^v1.11.0 2017-05-01 21:29:50 -06: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 installation instruction 2017-05-12 11:31:00 -07:00
analyzer.go Merge branch 'master' into consolidate-fs-files 2017-05-12 20:24:32 +03:00
analyzer_notwindows_test.go Add Windows specific function for making a file unreadable during tests. 2017-05-02 02:34:40 -04:00
analyzer_test.go test: move test to internal/test 2017-05-11 08:57:58 +10:00
analyzer_windows_test.go Add Windows specific function for making a file unreadable during tests. 2017-05-02 02:34:40 -04:00
appveyor.yml appveyor.yml: fix failure to detect windows build errors 2017-05-18 13:56:49 +10:00
context.go Merge branch 'master' into consolidate-fs-files 2017-05-12 20:24:32 +03:00
context_test.go move Logger into Ctx; restore logging 2017-05-11 11:16:36 -05:00
lock.go gps: move gps to internal/gps 2017-05-10 14:15:27 +10:00
lock_test.go test: move test to internal/test 2017-05-11 08:57:58 +10:00
manifest.go move Logger into Ctx; restore logging 2017-05-11 11:16:36 -05:00
manifest_test.go fixing first test. Still working on integration tests for gps 2017-05-13 23:25:13 -04:00
project.go Merge branch 'master' into consolidate-fs-files 2017-05-23 19:39:35 +03:00
project_test.go Add a leading underscore to vendor backup 2017-05-20 10:22:09 -05:00
test_project_context_test.go move Logger into Ctx; restore logging 2017-05-11 11:16:36 -05:00
txn_writer.go Add some logging to dep prune 2017-05-25 19:46:46 -05:00
txn_writer_test.go dep: unexport SafeWriter.LockDiff 2017-05-17 12:29:32 +10:00

README.md

Dep

Linux: Build Status | Windows: Build status | Code Climate

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/cmd/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 and FAQ 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.