This problem has come up on the list before [1]. The only way out I found was to remove the offending vendor directory from the project being vendored (or find a way that doesn't involve vendoring the equivalent of camlistore).
On 6 February 2017 at 19:30, Tamás Gulácsi <tgulacs...@gmail.com> wrote: > Shall we reorganize camlistore.org? (move vendor/ under > camlistore.org/cmd/vendor?) > This was my first thought too. Unfortunately (AFAIK) this doesn't work, since that only vendors the imports of `/cmd/` and not the imports of `/pkg/` (which presumably are meant to be vendored). I've not yet seen a good solution to this which avoids modifying the package being imported. Not ideal since it means you can't simply reference the remote code, but you need [reference + patch to remove vendoring]. [1] https://groups.google.com/d/topic/golang-nuts/AnMr9NL6dtc/discussion -- 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.
