vendetta
vendetta copied to clipboard
A minimal tool for managing golang project dependencies as submodules
Under Windows, say that I run this on my package `github.com/DanielOaks/oragono`, vendetta will then try to vendor my package `github.com/DanielOaks/oragono` under `vendor/github.com/DanielOaks/oragono`. Basically, I think it just doesn't recognise that...
In the case where you're vendoring a library which has vendored dependencies, building on the master project can cause problems (particularly if the vendored library shares types from third party...
In my case, it's because I make my directory a symlink into the full path in GOROOT ```shell $ go list . github.com/parsable/beacon SamV-WI:~/p/beacon $ vendetta Unable to infer project...
I'd like a way to update only specific vendored packages, rather than all packages at once. Ideally, the UX would be something like `vendetta update github.com/specific/package`. With the current flagset,...
- Navigate to the root of some Go repository - Run `vendetta` Expected behavior: some kind of usage text letting me know how to add, update, or remove specific dependencies....