3 ms·

"This change drops support for code.google.com and fixes test." How was packaging broken?

• deleted 11y ago
  [deleted]
• dz0ny 11y ago
  Some apps/packages still use packages hosted on code.google.com. Basicly you have to update dependency tree for packages that were hosted there. If you vendor packages then you are not immediately affected but it still poses a problem in long term.
• aikah 11y ago
  There is no central repository system in Go. No Maven, no rubygems, no packagist , ... code.google.com/foo/bar package is the physical address were go get command will fetch the package. If that address is broken then the code is broken. Go doesn't have a package manager either. Go Get is certainly not a package manager. So when you use a third party package you have to fork it somewhere. The problem is that 2 libraries with the same exact code are different packages if their address is different. So sometimes it becomes a bit insane to work with third party libraries if people start forking them for safety. I consider this whole package url thing as a design mistake. But most of the Go community sees no problem with it.