4 ms·
That's true. But the complaint was sullying his/her code with third party names.
by fnord123 10y ago
That's true. But the complaint was sullying his/her code with third party names.
- mattmanser 10y agoBut the reason you don't want to mention a third party is precisely because you may want to change that third party. And if you start maintaining a redirect on a site you control, what happens when you let the domain die because you never use it? The amount of HN people who have a personal domain listed in their profile that is dead because life got in the way is surprisingly high (including me until recently).
- fnord123 10y ago>And if you start maintaining a redirect on a site you control, what happens when you let the domain die because you never use it? Right. Either you trust that Github or whomever will always be there or you manage your own domain, or you vendorise and put your dependencies in tree. There are benefits and drawbacks to each approach. It's not magic and we're all adults.
- pjmlp 10y agoVendoring doesn't work when the moment to update a package arrives and the upstream has changed SCM repository. There is no way to avoid doing code changes in order to update the code that was vendored, this assuming that it isn't a binary package to start with.
- fnord123 10y agoIt does work. You head to `$GOPATH/src/github.com/coolpeople/coolpackage` and then do `git remote set-url origin https://gitlab.com/coolpeople/coolpackage` https://gitlab.com/coolpeople/coolpackage`. New uses of go get will not work, but it's not impossible to work this way. Alternatively, you use find . -name \*.go -exec sed -i 's:github.com/coolpeople/coolpackage:gitlab.com/coolpeople/coolpackage:' {} +`.