On Mon, Jul 27, 2015 at 4:45 PM, Michael Stapelberg <[email protected]> wrote: > As I tried to explain before, we cannot use your vendored copies, and the > tarballs we’ll create of your source code will not even contain the vendor/ > directory.
Sorry, I had totally forgotten that you said this. Please forgive me if you've already answered the following, but I can't find it above: what is the convention for dealing with backwards-incompatible changes in Go libraries? If the library author tags with semantic versions and bumps a major version, are you able to cope with that, even if there are some binaries that need the old version and some that need the new? > FWIW, the only blocker currently to get gcsfuse uploaded is > https://github.com/GoogleCloudPlatform/gcsfuse/issues/93 Cool. I've switched to codegangsta/cli itself, so I believe this shouldn't be an issue anymore. Tagged v0.4.0 for you to work from. _______________________________________________ Pkg-go-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
