On Sat, Jul 16, 2016 at 5:29 AM, Henrik Johansson <dahankz...@gmail.com> wrote: > For repeatable builds there are many ways and tools that work fine, Gb is > not unique in this respect. > > I don't get why this should be a controversial topic however. It seems to be > an issue only in the go community. > In all the other languages (newer more modern anyway) it is considered a > solved problem. > Sure different tools pop up now and then but they all work in the same > general way. > > I am sure there is a reason but why can't we just settle on the same idea > that everyone else is doing? > Applications and libraries would all then use the same principal way of > resolving dependencies and different tools could handle conflicts in > whatever way the author likes. Vendoring or not it would work regardless.
My understanding is that what other languages do also has problems. If there is a clear solution here, I certainly think we should adopt it. Can you explain what it is that other languages do, and how we should change to do the same thing? Ian -- 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 golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
