> >> Note, that this is essentially one of the workflows suggested here (which I >> would consider the canonical documentation for the "eng org wants to onboard >> Go" case): >> https://golang.org/ref/mod#private-modules > > I have realised a goproxy may be needed rather than a http server as I expect > a > domain with https, will be required for security despite being LOCALLY secure. >
>> Jim, I used replace this way just yesterday. It works fine, but is not easily >> discoverable as a process and it took me a minute or two to figure it out. It works well mostly but seems buggy at times. Saying functions aren't defined with illogical fixes like connecting the internet and "updating transitive dependencies. I'm starting to reluctantly come to the conclusion that I will simply have to spend the time setting up a GoProxy, to be in a more tested place. Having to occasionally delete empty lines and put them back seemingly randomly after a build tag is enough to deal with already. Maybe I should dos2unix all my files or something? -- 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/ce6d8693-c722-165d-6eee-5ac2e559a6a6%40gmail.com.
