<p>On the github page, it mentions that it is safe to use in production, although on the next line it still mentions it as an experiment. However I was wondering if it has already achieved adoption, or people are still using glide, godep, etc.?</p>
<hr/>**评论：**<br/><br/>dlsniper: <pre><p>Yes, they've already started to adopt dep, given all other package managers are started to be flagged as deprecated. Stop using anything else and switch to dep.</p></pre>jgillich: <pre><p>I did a quick search on GitHub:</p>
<ul>
<li><a href="https://github.com/search?utf8=%E2%9C%93&q=filename%3AGodeps.json&type=">19k projects are using Godep</a></li>
<li><a href="https://github.com/search?utf8=%E2%9C%93&q=filename%3Aglide.lock&type=">13k projects are using Glide</a></li>
<li><a href="https://github.com/search?utf8=%E2%9C%93&q=filename%3AGopkg.lock&type=">11k projects are using dep</a></li>
</ul>
<p>Definitely ready for production, it's actually incredible how well dep works considering what it does. Only once did I run into an issue because a project modified vendored deps (without forking), which is not something anyone should be doing, ever. Other than that, I'm 100% happy, and I've been using it for well over a year.</p></pre>emilevauge: <pre><p>We use it on <a href="https://github.com/containous/traefik" rel="nofollow">Traefik</a> and it was a great move (from glide).</p></pre>neoasterisk: <pre><p>I've been using godep and govendor on older projects. Switching to dep was seamless. I see no reason to go back. </p>
<p>That said, I still have some projects that use Heroku and unfortunately Heroku still does not support dep, which is sad.</p></pre>berfarah: <pre><p>That isn't true anymore: <a href="https://github.com/heroku/heroku-buildpack-go/blob/master/README.md" rel="nofollow">https://github.com/heroku/heroku-buildpack-go/blob/master/README.md</a></p>
<p>Been using dep on Heroku without any issues</p></pre>neoasterisk: <pre><p>Woot! I've been waiting months for this! </p></pre>scottjbarr: <pre><p>dep is absolutely ready for production use. We use it on every project we have, with the exception of the few projects with native dependencies which dep doesn't handle.</p></pre>csnate: <pre><p>Not open source, but we used dep for our dependency management. We went from using scripts and git subtrees to dep.</p></pre>rottenanon: <pre><p>to everyone in the thread who are using dep. Could you please help me if there's anything I can do to achieve the following:</p>
<p><a href="https://github.com/FiloSottile/gvt" rel="nofollow">Gvt</a> lets us define an import path different from the download path.</p>
<p>e.g.
Download path: github.com/user/pkg</p>
<p>Import path: user/pkg</p>
<p>It's just something we require in my company, I know it's not a standard usecase, but we need it.</p></pre>SonOfMotherDuck: <pre><p>Do you mean something like this:
<a href="https://golang.github.io/dep/docs/Gopkg.toml.html#source" rel="nofollow">https://golang.github.io/dep/docs/Gopkg.toml.html#source</a></p></pre>rottenanon: <pre><p>Oh boy, yes!</p></pre>ioddly: <pre><p>I shifted the one Go project I'm currently actively maintaining to it. No issues.</p></pre>F21Global: <pre><p>I've switched all my open-source and private projects from govendor and glide to dep. Dep has been pretty stable and usable for me.</p></pre>itachi_amaterasu: <pre><p>I tried to use <code>dep</code> in a Goa project. My only issue is that <code>dep</code> does not handle binary tools like the goa binary, which is a dependency if you have to use Goa. So, if your project uses <code>protobuf</code> or <code>golint</code> which require a binary to be executed from cmd line, you won't be able to use <code>dep</code>.</p>
<p>The only way around this is to use virtualgo - which to me is a bit of an overkill. Hence I went back to usual go-get style.</p>
<p>Relevant discussion here - <a href="https://github.com/golang/dep/issues/1572" rel="nofollow">https://github.com/golang/dep/issues/1572</a></p></pre>sacrehubert: <pre><p>Question: what are the kinds of problems/pain-points where I should be thinking "hmm... this is a sign that it's time to look into dep" ?</p></pre>dcuadrado: <pre><p>lack of support for private repos is stopping us from adopting it, so we are still using <code>glide</code></p></pre>diabetesjones: <pre><p>Dep is constantly broken for me and members of my team, from <code>init</code> hanging indefinitely, to <code>dep ensure</code> giving absolutely no output at all... I think it stems from a dependency having a non-existent dependency of it's own, based on some Github issues, but the speed and lack of output from running the dep commands make troubleshooting it more trouble than it's worth. Would love to get it working. It works seamlessly on one of our devs computers, he has had absolutely no issues, and is the only one. He can run any command, and though it's very slow and gives little output when it's being slow, it does eventually finish running successfully. Github issues seem to have a lot of people not being able to get past <code>init</code>. I can't recommend it but I'm sure it will be more stable soon. </p>
<p>The most frustrating part is it's lack of error outputting. If you don't have <code>hg</code> installed (Mercurial) on ubuntu, dep just hangs forever with no output at all, or timeout cancelling it. No <code>you need hg!</code>, even with <code>-v</code>. This is so hard to diagnose - basically only by going to the Github issues and seeing if someone else has your problem! </p>
<p>In comparison, Glide works every time on everyone's computer, so we will wait to migrate to dep until it's stable. YMMV but dep has been a headache.</p></pre>Removalsc: <pre><p>I had hanging problems on Ubuntu, <code>-v</code> helped diagnosing it though. It was a problem with git not being authorized to download from a private repo. Ending up having to cache the credentials and then run it. For some reason using keys didnt work.</p>
<p>Dep should stop and prompt for the creds, but instead it just sits there doing nothing.</p></pre>colek42: <pre><p>I found it hangs under the following conditions.</p>
<ol>
<li> You have circular dependency issues at the repo level.</li>
<li> Large submodules in your dependencies.</li>
<li> Github credentials not cached, no ssh keys.</li>
<li> known hosts file is not updated.</li>
</ol>
<p>We just fixed these issues in our CI/CD and common repo and it works great.</p></pre>peterbourgon: <pre><p>Great report! Would you mind linking to the issues you filed, so I can watch them?</p></pre>
