Golang package management
0 likes301 views
Problems: Decentralised version management No explicit concept of versions go get always pulls from the HEAD of the default branch in the repository Development vs Production environment Solutions: gopkg.in godep govendor GO15VENDOREXPERIMENT=1
![github.com/kardianos/govendor
File: vendor.json
Advanced control
Ignore test files and other build tags
Migrate [auto, godep, internal, vendor]
Vendor: std. library packages, local, external & etc.](https://image.slidesharecdn.com/golangpackagemanagement-151010095937-lva1-app6892/85/Golang-package-management-6-320.jpg)
Golang package management
- 1. Package version management Github: ernestas-poskus Twitter: ernestas_poskus
- 2. Problems Decentralized version management No explicit concept of versions go get always pulls from the HEAD of the default branch in the repository Development vs Production environment
- 3. Package manager Adhere to the stable HEAD philosophy. Default branch must always be the stable, released version of your package. New major versions of your package must have their own repository. Industry standard is to use tags and branches for marking multiple versions.
- 4. gopkg.in Provides versioned URLs Handles git branches and tags for versioning Encourages the adoption of stable versioned package APIs. E.g.: http://gopkg.in/linkosmos/tokeq.v0
- 5. github.com/tools/godep File godeps.json Simple: godep save/restore Works with $GOPATH
- 6. github.com/kardianos/govendor File: vendor.json Advanced control Ignore test files and other build tags Migrate [auto, godep, internal, vendor] Vendor: std. library packages, local, external & etc.
- 7. GO15VENDOREXPERIMENT=1 Uses vendor/ if exists. Code inside vendor/ subtrees is not subject to import path checking. Recursive vendoring.
- 8. What to use ? export GO15VENDOREXPERIMENT=1 govendor / godeps gopkg.in