You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 9, 2020. It is now read-only.
Copy file name to clipboardExpand all lines: FAQ.md
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,11 @@ Committing the vendor directory is totally up to you. There is no general advice
39
39
-[@sdboyer in #371](https://github.com/golang/dep/issues/371#issuecomment-293246832)
40
40
41
41
## 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.
42
45
46
+
Here are some suggestions for when you could use `dep` or `go get`:
43
47
> I would say that dep doesn't replace go get, but they both can do similar things. Here's how I use them:
44
48
>
45
49
> `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