Hello,
While toying in some projects i ended using go mod replace directive to
point to a local directory containing a git clone of a remote, that i know
will need some modifications.
something like
$ git clone github.com/anacrolix/dht dht
$ cat go.mod
module github.com/clementauger/dplay
go 1.16
replace github.com/anacrolix/dht => ./dht
require (
github.com/anacrolix/dht v1.0.1 // indirect
github.com/anacrolix/dht/v2 v2.9.0 // indirect
)
is it intended or am i over using it ?
Do you recommend to commit the remote into my repository to keep my dirty
fork along the rest of the code and keep things straight forward to re
compile ?
Do you think it is a good idea to map the local fork to a remote branch as
part of a larger model to drive code management ?
i would prefer to get that right upfront, i know the pain i will have to
handle mass import path update, it is so terribly boring (and gomod has
made it easy so far!).
I might have missed it but i can not find much about these in
https://blog.golang.org/using-go-modules
I also gave a try to https://www.google.com/search?q=go+mod+best+practices
It is not very helpful.
thanks for interest and suggestions.
--
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/aa8f5972-053e-4d03-900a-9b18c26b4754n%40googlegroups.com.
