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.
FWIW, the only blocker currently to get gcsfuse uploaded is https://github.com/GoogleCloudPlatform/gcsfuse/issues/93 On Mon, Jul 27, 2015 at 1:24 AM, Aaron Jacobs <jaco...@google.com> wrote: > Hi Michael, > > On Fri, Jun 12, 2015 at 9:12 AM, Aaron Jacobs <jaco...@google.com> wrote: > > Question: what would the situation look like if gcsfuse instead > 'vendored' its > > dependencies, so that the exact version it depends on was included in > its git > > repo and it was built with a tool like godep ( > https://github.com/tools/godep) > > or nut (https://github.com/jingweno/nut)? > > I'm resurrecting the question above, because as of commit 2eb17b6, gcsfuse > has > its dependencies vendored. (For the standard reason: it makes it much much > easier to get a reproducible build, insulates against > backwards-incompatible > API changes, etc.) How does Debian generally treat such project? I > apologize if > this causes a bunch of extra work. > > Aaron > -- Best regards, Michael
_______________________________________________ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
