4 ms·

About as much extra effort as it's saving the end users (devs) from having to find and download the package in the first place. And you could just tell your us

by Vendan 10y ago

About as much extra effort as it's saving the end users (devs) from having to find and download the package in the first place. And you could just tell your users to download from your site and stick it in their gopath, so it's literally just an enhancement over the model you are wanting, just allows an author to spend a few minutes to save every user some time...

pjmlp 10y ago
When a package author changes the SCM repository location of a Java package available on any Maven like repository, I don't have to do anything. And he/she also don't have do any extra work so that I can keep using the same package names.
- Vendan 10y ago
  And there is literally nothing preventing that from functioning with Go. All you are complaining about is that the central "package repository" doesn't exist yet, where as my point is that Go has given you all the tools to build a central or distributed repository as you choose. You seem to be most upset that people are just using GitHub cause it's free and it works, and how is that different then any other central repository?
  - pjmlp 10y ago
    URLs are part of package name and there is no guarantee they will survive a repository change unless the package author has taken the effort to use canonical imports. As for being upset, not really, unless my boss requires me to use Go, I don't plan using it again.
- themihai 10y ago
  In practice the author rarely changes the import domain/url so it's not really an nuisance. There are tools to fix imports if the unlikely case actually happens. I value the fact that I don't need config files to make it work more than this small possible inconvenience. There is also a `alias` feature in the upcoming version which allows the author to make the transition from one path to another even easier for clients. https://godoc.org/golang.org/x/tools/refactor/rename https://godoc.org/golang.org/x/tools/refactor/rename

by Vendan 10y ago

pjmlp 10y ago

When a package author changes the SCM repository location of a Java package available on any Maven like repository, I don't have to do anything. And he/she also don't have do any extra work so that I can keep using the same package names.

Vendan 10y ago
And there is literally nothing preventing that from functioning with Go. All you are complaining about is that the central "package repository" doesn't exist yet, where as my point is that Go has given you all the tools to build a central or distributed repository as you choose. You seem to be most upset that people are just using GitHub cause it's free and it works, and how is that different then any other central repository?
- pjmlp 10y ago
  URLs are part of package name and there is no guarantee they will survive a repository change unless the package author has taken the effort to use canonical imports. As for being upset, not really, unless my boss requires me to use Go, I don't plan using it again.
themihai 10y ago
In practice the author rarely changes the import domain/url so it's not really an nuisance. There are tools to fix imports if the unlikely case actually happens. I value the fact that I don't need config files to make it work more than this small possible inconvenience. There is also a `alias` feature in the upcoming version which allows the author to make the transition from one path to another even easier for clients. https://godoc.org/golang.org/x/tools/refactor/rename https://godoc.org/golang.org/x/tools/refactor/rename