Since you removed the vendor/ directory from jitsi/jap, everything is working as expected, right?
On Tue, Jul 5, 2016 at 8:46 PM, Sam Whited <s...@samwhited.com> wrote: > On Tue, Jul 5, 2016 at 1:37 PM, Peter Bourgon <pe...@bourgon.org> wrote: >> As of today, if your binary vendors any other package, you need to >> ensure that package doesn't have a vendor/ directory anywhere in the >> source tree. Library maintainers can be good citizens by ensuring >> their libraries don't vendor their dependencies; this is how the >> jitsi/jap repo exists today, which is fine. But the responsibility is >> ultimately on you; you can manually remove the vendor/ directory of >> your vendored deps, or you can use a tool that does it automatically. > > I didn't follow this; the library *doesn't* have any vendor/ dir, nor > do any of the other things the application has vendored. > > —Sam > > > > -- > Sam Whited > pub 4096R/54083AE104EA7AD3 > https://blog.samwhited.com -- 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.
