<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>davecheney</author><text>Hi HN,&lt;p&gt;There was a video recorded at this meetup, but I&amp;#x27;m not in control of that.&lt;p&gt;In the mean time, the getting started document [1] is the contents of the &amp;quot;demo time&amp;quot; slide.&lt;p&gt;1. &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;constabulary&amp;#x2F;gb&amp;#x2F;blob&amp;#x2F;master&amp;#x2F;getting-started.md&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;constabulary&amp;#x2F;gb&amp;#x2F;blob&amp;#x2F;master&amp;#x2F;getting-start...&lt;/a&gt;</text><parent_chain></parent_chain></comment><story><title>Reproducible Builds in Go</title><url>http://go-talks.appspot.com/github.com/davecheney/presentations/reproducible-builds.slide</url><text></text></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>ghodss</author><text>One major limitation of this approach is that any project that wishes to vendor or lock their dependencies can no longer be used as a dependency for another project. From the gb GitHub:&lt;p&gt;&amp;gt; A project is the consumer of your own source code, and possibly dependencies that your code consumes; nothing consumes the code from a project.&lt;p&gt;This seems to imply that any code &lt;i&gt;outside&lt;/i&gt; of a project (i.e. the code inside vendor&amp;#x2F;src) has no recourse for indicating the versions of their dependencies. This is nice in that it simplifies the problem, but to completely remove the ability for any and all libraries to indicate the versions of their dependencies seems unnecessarily restrictive. If I build a library for others to use, and I have a dependency, I want to be be able to lock to a specific version, or at least give my preference for a version.&lt;p&gt;Of course, this creates its own issues - what do you do when two libraries depend on two different versions of the same library? (Also known as the diamond dependency problem.) This is where the Go culture helps, where as long as you pick a later version, things are likely to work. But I&amp;#x27;d rather have the tooling let me detect the two versions that the two libraries want, show that there is a mismatch, and give me the ability to override and pick one (probably the later one). Instead, the gb approach eliminates the ability for the libraries to even have the ability to indicate what version they would prefer, which makes it even more difficult to get a bunch of libraries that share dependencies to work correctly together.&lt;p&gt;godep (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;tools&amp;#x2F;godep&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;tools&amp;#x2F;godep&lt;/a&gt;) seems to have the best compromise: vendor dependencies without path rewriting (though with GOPATH rewriting), but also keep track of their versions in a Godep.json file. You can gracefully pick between conflicting versions upstream if need be.</text><parent_chain></parent_chain></comment><story><title>Reproducible Builds in Go</title><url>http://go-talks.appspot.com/github.com/davecheney/presentations/reproducible-builds.slide</url><text></text></story>