Read on Twitter
Ohhh... so whether `go get` succeeds or not depends on the directory you are in... MAKES PERFECT SENSE AMIRITE FGDSFDS
So....... If you are in a directory that belongs to a go module, go get fails with a lousy error message if the package (=repo sense of the word) you are trying to get isn't a go module? I must be misunderstanding something, ...
...but how do they expect people to migrate to modules if you can't depend on non-modules; that's a chicken-and-egg problem?
No, that can't be it. I'm getting errors even with a forked and module-ized dependency. But the error message is too cryptic to be actionable...
My Go problems (for now) finally are about to resolve. It seems that while they are, thank god, getting rid of GOPATH, they are introducing more destructive environment variables... (GOPRIVATE, GOPROXY, GOSUMDB...) This thread saved me. https://github.com/golang/go/issues/35164
