This seems a noddy question but can't easily find an answer with Google
apparently. I may have lost the plot :-)
There is a repo which contains source for a go executable that I want to
use.
Normally I install this with: go install original.domain/path@latest
I want to fork that repo and make some experimental changes.
So then I want to: go install my.forked.domain/path@commit
But if I don't also change the go.mod file in my fork I get something like:
go: downloading my.forked.domain/path v0.0.0-20221203102529-commit
go: my.forked.domain/path@commit:
my.forked.domain/path@v0.0.0-20221203102529-commit:
parsing go.mod:
module declares its path as: original.domain/path
but was required as: my.forked.domain/path
Obviously I could change the go.mod in my fork, but that seems wrong if I
later want to submit a PR on the original repo.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/9a9542bd-1718-4ea7-a0ed-42b343bb9699n%40googlegroups.com.
