3 ms·
Yet go is a dependency nightmare! Dealing with more than one developer on a project with dependencies is incredibly difficult due to the insane decision to not
by hox 13y ago
Yet go is a dependency nightmare! Dealing with more than one developer on a project with dependencies is incredibly difficult due to the insane decision to not support locking a dependency to a specific version.
- mitchty 13y agoOur quick "solution", was just tar cvf up the dependencies and use that. Alternatively godep as noted below, or you could get creative with git submodules or clone the repos to a local cache. The reason go is simpler is you only need to deal with this at compile time, and thats what the ci server is for. My goal is removing runtime checks for crap and dealing with package versions every time I update things. Go is more akin to c really here, and in my not so humble opinion it is a simpler task to sort out dependencies at compile time than on every system I need to deploy to.
- regularfry 13y agoI'm actually quite interested in how to fix that. The naive solution that springs to mind is sticking a local cache between my dev environment and the upstream sources, where I can control precisely what versions are available. Is that doable?
- mh- 13y agohave a look at godep: https://github.com/kr/godep https://github.com/kr/godep
- regularfry 13y agoPrecisely the sort of thing I'm looking for. Thanks!