Nix + Go | 228 Members | |
| Go packaging for and with Nixpkgs. | Be excellent to each other. | 51 Servers |
| Sender | Message | Time |
|---|---|---|
| 30 May 2025 | ||
| I think I can live with that given that there is still a vendor hash | 18:34:55 | |
| go's tooling already handles that with the module cache (albeit per-user) | 18:35:14 | |
| yeah, I know | 18:35:25 | |
| my issue is that it feels counter-nixy, but it is probably me, that's why I was asking | 18:35:49 | |
| 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 | |
| and the cache files are read-only so unless you intentionally try to break them... | 18:38:28 | |
| Yeah, that's probably ok | 18:38:29 | |
| the derivations are also build from fresh, if I understood the code right | 18:39:22 | |
| I guess they need to, if the build is sandboxed | 18:39:32 | |
| 20:15:18 | ||
| 20:16:24 | ||
| 1 Jun 2025 | ||
| 15:33:28 | ||
| 23:48:05 | ||
| 2 Jun 2025 | ||
| 08:36:51 | ||
| 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 | |
| * 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 | |
| * 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 | |
| * 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 | |
| * 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?
| 16:28:30 | |
| update:
| 16:32:19 | |
| yep, router built in 28 minutes, rpi in 8.5 | 17:25:48 | |
| Some weird I/O bottleneck? | 17:27:41 | |
| I do suspect something like this, but got no clue how to verify. I'm running this on AMD CPUs and Intel N6005, it also seems tightly related to nix build environment, it builds perfectly fine as a standalone project outside Nix | 17:31:24 | |
| I'd be up for any pointers on how to analyze the situation | 17:50:23 | |
perf top? | 17:54:58 | |
| 4 Jun 2025 | ||
| 19:23:35 | ||
| having some trouble in https://github.com/NixOS/nixpkgs/pull/414070, I'm trying to get the version command to work correctly but it's still not despite me adding the ldflags from the goreleaser | 22:05:15 | |
| 5 Jun 2025 | ||
| What workflow do you typically use to develop in a nix shell? I have some minor trouble with the dependencies: If I just go in a dev shell (i.e. with
The other minor issue is that I need to change the From this experience, it seems that running the configure phase is a better approach, but it contradicts a bit what me and @jrick discussed a few days ago, from which I understood (perhaps wrongly) that using go tools directly was preferred. Curious about what other people are doing :) | 04:46:00 | |
| Has anyone got a decent solution to build go projects with private dependencies? | 05:03:22 | |
| how are you making the devShell? if you use it directly via a package, that's gonna happen | 05:55:30 | |