You can also try using workspace support implemented in Go 1.18.
Create a go.work file in ~go/pkg using
`go work init`
and add all your modules using
`go work use -r .`
Manlio Perillo
On Monday, April 25, 2022 at 11:38:36 PM UTC+2 darse...@gmail.com wrote:
> Sean. Brilliant. I don't grasp how
Sean. Brilliant. I don't grasp how I missed the file:// setting. Works
beautifully and I am a grateful Gopher. THANK YOU.
On Monday, April 25, 2022 at 5:15:33 PM UTC-4 se...@liao.dev wrote:
> See https://go.dev/ref/mod#environment-variables
>
> GOPROXY=file://$(go env GOMODCACHE)/cache/download
See https://go.dev/ref/mod#environment-variables
GOPROXY=file://$(go env GOMODCACHE)/cache/download
- sean
On Mon, Apr 25, 2022 at 10:08 PM David Arsenault
wrote:
> Hello. I was hoping to get some smart advice on a problem using go on a
> closed network.
>
> Summary:
> - closed network, no ou
Hello. I was hoping to get some smart advice on a problem using go on a
closed network.
Summary:
- closed network, no outside access (painful, I know)
- moved all needed packages to ~/go/pkg...
- using go modules
Problem:
go mod insists on using the network (can't). When I set GOPROXY=off go mo
