| 30 May 2025 |
 samuel | yeah, exactly. I think what I would like is a specific GOMODCACHE AND GOPATH for each nix shell | 18:29:35 |
| samuel | * yeah, exactly. I think what I would like is a specific GOMODCACHE and GOPATH for each nix shell | 18:29:47 |
| samuel | 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 |
| samuel | 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 |
| samuel | which is convenient, but was counter intuitive at first | 18:34:32 |
| samuel | 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 |
| samuel | yeah, I know | 18:35:25 |
| samuel | my issue is that it feels counter-nixy, but it is probably me, that's why I was asking | 18:35:49 |
| jrick | go cryptographically verifies the dependencies too so you're not going to risk building from different sources even if there is some download duplication | 18:37:19 |
| jrick | and the cache files are read-only so unless you intentionally try to break them... | 18:38:28 |
| samuel | Yeah, that's probably ok | 18:38:29 |
| samuel | the derivations are also build from fresh, if I understood the code right | 18:39:22 |
| samuel | I guess they need to, if the build is sandboxed | 18:39:32 |
|  sleroq changed their profile picture. | 20:15:18 |
| sleroq changed their profile picture. | 20:16:24 |
| 1 Jun 2025 |
|  Ghil joined the room. | 15:33:28 |
|  Sean Thawe joined the room. | 23:48:05 |
| 2 Jun 2025 |
|  Frédéric Christ changed their display name from Frédéric Christ (🧳 12.05. - 02.06.) to Frédéric Christ. | 08:36:51 |
 kdn | Anyone else observed an issue with building Go projects from source using Nix taking upwards of 10 minutes (usually ~20/25/30/35)?
It drives me nuts on both of my NixOS setups to wait ~1 hour to build both Netbird and Terraform on updates... | 16:23:23 |
| kdn | * Anyone else observed an issue with building Go projects from source using Nix taking upwards of 10 minutes (usually ~20/25/30/35)?
It drives me nuts on all (checked x86 desktop and laptop so far, trying the x86 router now) of my NixOS setups to wait ~1 hour to build both Netbird and Terraform on updates... | 16:24:58 |
| kdn | * Anyone else observed an issue with building Go projects from source using Nix taking upwards of 10 minutes (usually ~20/25/30/35)?
It drives me nuts on all (checked x86 desktop and laptop so far, trying the x86 router & rpi4 now) of my NixOS setups to wait ~1 hour to build both Netbird and Terraform on updates... | 16:25:42 |
| kdn | * Anyone else observed an issue with building Go projects from source using Nix taking upwards of 10 minutes (usually ~20/25/30/35) with pretty much zero CPU activity?
It drives me nuts on all (checked x86 desktop and laptop so far, trying the x86 router & rpi4 now) of my NixOS setups to wait ~1 hour to build both Netbird and Terraform on updates... | 16:26:48 |
| kdn | * Anyone else observed an issue with building Go projects from source using Nix taking upwards of 10 minutes (usually ~20/25/30/35) with pretty much zero CPU activity?
- building everything off https://github.com/nazarewk-iac/nix-configs
- It drives me nuts on my NixOS setups (brys desktop & oams laptop) to wait ~1 hour to build both Netbird and Terraform on updates...
- trying the x86 router (etra) & rpi4 (briv) now, those have slightly different setups
| 16:28:30 |
| kdn | update:
rpi4 finished building subpackage client and started management of netbird in 4 minutes- router still builds subpackage client after 8 minutes
| 16:32:19 |
| kdn | yep, router built in 28 minutes, rpi in 8.5 | 17:25:48 |
| K900 ⚡️ | Some weird I/O bottleneck? | 17:27:41 |
