4 ms·
This is (sadly) why gopkg.in [1] exists. It proxies Git repositories, mapping: gopkg.in/mypackage.v3 -> github.com/go-mypackage/mypackage gopkg.in/bob
by lobster_johnson 11y ago
This is (sadly) why gopkg.in [1] exists. It proxies Git repositories, mapping:
gopkg.in/mypackage.v3 -> github.com/go-mypackage/mypackage
gopkg.in/bob/mypackage.v3 -> github.com/bob/mypackage
...where v3 is a branch or tag named v3, v3.N or v3.N.M.
What Go needs is a real package manager that uses the new 1.5 vendor directory to manage dependencies. There have been some attempts (godep, gb), but they aren't very good, especially if you look at how existing languages have solved this (Ruby's Bundler, Rust's Cargo).
[1] https://gopkg.in https://gopkg.in