2 ms·
How do you manage dependency versions with a fully-qualified package name?
by troutwine 14y ago
How do you manage dependency versions with a fully-qualified package name?
- skybrian 14y agoThere's no explicit versioning unless you do a fork (which effectively puts the version into the import path). When doing open source work, you just assume that the latest version works. If it doesn't, you can complain and check out an earlier version instead (locally), or in the worst case, fork the code until it's fixed and change your import statements to point to the forked version. For a company, it makes sense to check your GOPATH into your own source control system, so everyone has the same version of the open source libraries you're using. Then upgrading some open source libraries to a new version is a commit like any other change.