| 30 May 2025 |
 jrick | GOMODCACHE will override where modules are downloaded to | 18:27:52 |
| jrick | it can also be cleared at any time with go clean -modcache | 18:28:39 |
 @s_r:matrix.org | yeah, exactly. I think what I would like is a specific GOMODCACHE AND GOPATH for each nix shell | 18:29:35 |
| @s_r:matrix.org | * yeah, exactly. I think what I would like is a specific GOMODCACHE and GOPATH for each nix shell | 18:29:47 |
| @s_r:matrix.org | so that you don't get binaries pulled from your home | 18:30:06 |
 K900 ⚡️ | I'm pretty sure you can do that with buildGoModule? | 18:30:21 |
| K900 ⚡️ | Though you'll have to keep your vendorHash in sync | 18:30:34 |
| jrick | forget GOPATH exists, the ones that matter are GOCACHE and GOMODCACHE | 18:31:18 |
| @s_r:matrix.org | I guess the thing that got me thinking about this is that I need to download any given module once, the first time I need it, but then I don't need to do that again even if I'm in a different shell | 18:34:07 |
| @s_r:matrix.org | which is convenient, but was counter intuitive at first | 18:34:32 |
| @s_r:matrix.org | I think I can live with that given that there is still a vendor hash | 18:34:55 |
| jrick | go's tooling already handles that with the module cache (albeit per-user) | 18:35:14 |
| @s_r:matrix.org | yeah, I know | 18:35:25 |
