Skip to content
This repository was archived by the owner on Sep 9, 2020. It is now read-only.

Commit 15de9b0

Browse files
committed
Add caveats to dep vs. go get answer
1 parent db0acd4 commit 15de9b0

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

FAQ.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,11 @@ Committing the vendor directory is totally up to you. There is no general advice
3939
-[@sdboyer in #371](https://github.com/golang/dep/issues/371#issuecomment-293246832)
4040

4141
## Does `dep` replace `go get`?
42+
No, `dep` is an experiment and is still in its infancy. Depending on how this
43+
experiment goes, it may be considered for inclusion in the go project in some form
44+
or another in the future but that is not guaranteed.
4245

46+
Here are some suggestions for when you could use `dep` or `go get`:
4347
> I would say that dep doesn't replace go get, but they both can do similar things. Here's how I use them:
4448
>
4549
> `go get`: I want to download the source code for a go project so that I can work on it myself, or to install a tool. This clones the repo under GOPATH for all to use.

0 commit comments

Comments
 (0)