with it <https://github.com/Masterminds/glide>). I've worked with package
management in PHP <http://getcomposer.org/>, node.js <http://npmjs.org/>,
Python <https://pypi.python.org/pypi/pip/>, Ruby <http://rubygems.org/>,
and other languages. The Go community appears to be doing a number of
things differently than these other tools and communities (or at least in
the publicly talked about sense) and I'm wondering why. Let me explain.
In most of these other languages a typical workflow is to have a file
describing the dependencies and their versions. The versions are important
for reproducible builds. In each environment, whether it be development,
CI, or other places, the tooling reads this file and fetches the
dependencies (sometimes from a mirror). The dependencies are stored in a
vendor directory but it's not stored in your projects SCM.
This is a section from a PHP project in JSON as an example.
Can someone explain why Go developers aren't looking to work in a similar
manner? Why vendoring in an SCM, not handling versions, and some other
habits are so prevalent?
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
For more options, visit https://groups.google.com/d/optout.