3 ms·
You're not dependent on GitHub. If you ever decide to switch to, say, sourcehut, you can keep the install command and not break anything. It also looks way nic
by unsafecast 4y ago
You're not dependent on GitHub. If you ever decide to switch to, say, sourcehut, you can keep the install command and not break anything.
It also looks way nicer, and it's easier to deal with (I'd rather type `import ”robpike.io/ivy”` than a GitHub link), but that's a flaw in the way go does packages imo
- cpach 4y agoAh. Interesting. I see that requesting https://robpike.io/ivy@latest https://robpike.io/ivy@latest yields a 302 that points to http://godoc.org/robpike.io/ivy@latest http://godoc.org/robpike.io/ivy@latest (not sure exactly what go install would do with that URL though)
- p4bl0 4y agoMaybe it doesn't do this redirect if the user agent is the one of go install? It would be a convenient way to have the package url works for both the package itself and its documentation :). EDIT: well now for me it redirects to: https://github.com/golang/go/issues/43036 https://github.com/golang/go/issues/43036 so… whatever is happening here might not be on purpose, actually.
- unsafecast 4y agoAs far as I know, ‘go get’ (not install; that's different) uses git to download a repository.
- unsafecast 4y agoOh, sorry. It's install after all. I assumed it's a library.
- icholy 4y agohttps://robpike.io/ivy@latest?go-get=1 https://robpike.io/ivy@latest?go-get=1