3 ms·

Having uniquely-named packages is insufficient unless the maintainers of those packages never update them. The point of tools like Bundler is not about name res

by al2o3cr 13y ago

Having uniquely-named packages is insufficient unless the maintainers of those packages never update them. The point of tools like Bundler is not about name resolution, it's about VERSION resolution. Sample size of 1, but here's a story about what happens when things go wrong: https://www.kickstarter.com/projects/2066438441/haunts-the-manse-macabre/posts https://www.kickstarter.com/projects/2066438441/haunts-the-m... The bit about packages from github.com being edited locally was particularly hair-raising. Really hope the smart folks working on Go figure out a resolution for this kind of thing.

NateDad 13y ago
The bit about packages being edited locally shows the problem was between the chair and keyboard, not in the language. That's like making edits to some local files and never pushing them up into source control. Of course it'll never work outside your own local machine. There are practices and tools for insulating yourself from changes to third party packages. Generally the answer is to copy the code into your own repo so that you control when it gets updated. There are tools that will do this automatically for you, and it's what most big Go projects do.