4 ms·
The project structure is fighting againts norms. The author should not have src checked in. They should have their package as the root so it is "go get-able" an
by sethammons 9y ago
The project structure is fighting againts norms. The author should not have src checked in. They should have their package as the root so it is "go get-able" and does not require the user to alter their GOPATH. To ensure that the proper dependency versions are present, they should vendor the dependencies. I would have opened an issue on GitHub for them, but I am not signed in currently. Cheers on releasing a neat tool.
EDIT: got off my mobile and to a laptop and submitted https://github.com/twitchyliquid64/subnet/issues/3 https://github.com/twitchyliquid64/subnet/issues/3.
- genieyclo 9y agoGood job! I'm looking into trying Go soon, is there something you'd recommend looking at for learning the Go ecosystem norms?
- sethammons 9y agoThe first is doing the tour at golang.org, then reading Effective Go at https://golang.org/doc/effective_go.html https://golang.org/doc/effective_go.html. There are lots of good reads at the golang blog, such as https://blog.golang.org/organizing-go-code https://blog.golang.org/organizing-go-code. I really enjoy Go, and hope you do too!
- twitchyliquid64 9y agoThanks! This is definitely something I need to get around to once I read up a bit more on vendoring.
- freedomben 9y agoCheck out the `dep` tool: https://github.com/golang/dep https://github.com/golang/dep It is the future of official vendoring tools. You could also look at `govendor`: https://github.com/kardianos/govendor https://github.com/kardianos/govendor I've used govendor in some projects and found it agreeable. Best of luck :-)
- weitzj 9y agoCheckout https://github.com/cloudflare/hellogopher https://github.com/cloudflare/hellogopher to get you started with a nice workflow. Uses gvt for vendoring. Tests over multiple packages are globbed correctly