Speaking as a new Gopher, but I have had lots of experience with software dependencies. A tool like dep would be perfect for this. You could simply pin the one dependency until a fix is provided for the error, and for the others you can simply keep updating to the latest.
This may not be the only time this happens and having the tools in place to handle it would make it very trivial to fix in the future. -bobby On Tuesday, October 31, 2017 at 11:43:21 AM UTC-7, Travis Keep wrote: > > Somebody I depend on for my project made a breaking change to their git > repo and broke my build. > > I found that if I simply revert their latest commit locally that my > project builds. > > I don't necessarily want to vendor everything because most of the > libraries I use I trust. But I do want to vendor the one git repo whose > owner keeps making breaking changes. > > I looked at dep, but dep seems to vendor everything. I don't want that. I > just want to vendor the one unstable library, and simply use HEAD for > everything else. > > What is the best way for me to proceed? > > Thanks in advance, > > > > -- 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.
