3 ms·
My main misery with modules was due to people renaming their GitHub repositories
by ithkuil 5y ago
My main misery with modules was due to people renaming their GitHub repositories
- jayd16 5y agoFork them (just make a copy you own) so you have control?
- ithkuil 5y agoUsually my problems are with transitive dependencies. I would have to fork quite a few projects to deal with that. I wish there was a more systematic way to do "replace", possibly in libraries as well
- thiht 5y agoThere’s a « replace » directive in go.mod.
- ithkuil 5y agoYeah I know, but it's suboptimal. If you use it your module cannot be "go install" lled, and it doesn't work for libraries
- acchow 5y agoReplace in go.mod breaks `go install`?
- ithkuil 5y agoOh yeah, this used to work but some go version ago it stopped working. See https://github.com/golang/go/issues/44840 https://github.com/golang/go/issues/44840
- jatone 5y agoglad other people see that as a problem as well. it irritates me to no end esp considering possible solutions are fairly straight forward but people can't get buyin from the golang team. for the record it stopped working in go 1.15. 1.14 was the last version it worked in.