Hello everyone,

We've been running into a vendoring issue regarding our toolset recently. 
Namely, breaking changes to gomobile will happen within one of our release 
cycles (such 
as 
https://github.com/golang/mobile/commit/2f75be449fbada35ca42f481f9878ba7f02a7e7d
 
), and cause our builds to break. Is there a means by which we can 
effectively vendor gomobile as a command, or ought we fork it and merge 
with upstream every so often? Changing our build scripts to point to a fork 
isn't a big deal, but I was wondering how others here have solved this 
problem.

-- Matt

-- 
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.

Reply via email to