Failed to go-get v2 about cc

[cznic]

Just a theory, but maybe the final /v2 in an url that has no .mod file is not supported by Go 1.11.

I hoped that I can just ignore modules, but frankly, I am starting to hate them.

Anyway, if you know a solution that can keep me ignoring modules and at the same time suport people that want or need to use them, please advise, thank you.

[cznic]

s/url/import path/ ofc.

[kortschak]

Just a theory, but maybe the final /v2 in an url that has no .mod file is not supported by Go 1.11.

This is indeed true as far as I'm aware.

Anyway, if you know a solution that can keep me ignoring modules and at the same time suport people that want or need to use them, please advise, thank you.

Unfortunately, I don't think this is tenable in the longer term. You can say use GO111MODULE=off or only build in $GOPATH, but these will eventually not work AFAIU.

I too am still coming to terms with these things.

[hajimehoshi]

Anyway, if you know a solution that can keep me ignoring modules and at the same time suport people that want or need to use them, please advise, thank you.

I'm afraid I don't have a good idea. I was wondering why you don't want to put go.mod.

[cznic]

I'm not against a .mod file in the repository. I just want to keep working solely inside my dead simple GOPATH="$HOME" and ignore modules. I'm not against the feature, obviously there are entities needing it for legitimate reasons. But I don't get why it has to affect those who don't need it.

Can I do go mod init in the root of this repository, git {add,commit,push} the go.mod file, list it in my local .gitignore, delete my local copy of go.mod and be happy?

Would that provide you and others with module support and let me keep my current workflow and allow me to somehow ignore modules?

cc @kortschak, your insights are very welcome, thank you.