Nix + Go | 221 Members | |
| Go packaging for and with Nixpkgs. | Be excellent to each other. | 47 Servers |
| Sender | Message | Time |
|---|---|---|
| 13 Nov 2024 | ||
Download image.png | 01:07:24 | |
| 22:15:34 | ||
| 15 Nov 2024 | ||
| 23:01:09 | ||
| 17 Nov 2024 | ||
| 03:23:02 | ||
| I'm experimenting with new Go builders for Nix and would like to invite people to take a look https://github.com/adisbladis/gobuild.nix/ | 03:26:19 | |
| 19 Nov 2024 | ||
| 21:15:52 | ||
| 20 Nov 2024 | ||
| 00:59:17 | ||
| 26 Nov 2024 | ||
| 03:14:23 | ||
| 5 Dec 2024 | ||
| 18:43:06 | ||
| 6 Dec 2024 | ||
| 21:16:47 | ||
| 9 Dec 2024 | ||
| Any thought on https://github.com/NixOS/nixpkgs/pull/363617? Would love to get some feedback on the idea. | 15:47:23 | |
| 11 Dec 2024 | ||
| 14:19:10 | ||
| 17 Dec 2024 | ||
| 12:03:58 | ||
Hello, when running "go run ." in nixos I get the error message "go: creating work dir: stat /tmp/nix-shell-59259-0: no such file or directory" how do I make it build for testing? | 12:05:17 | |
Can you paste the output of go env? | 12:09:15 | |
go: creating work dir: stat /tmp/nix-shell-94646-0: no such file or directory | 12:10:43 | |
| it works if i create that dir and runs a command on that shell session. Moving to another it wants a new directory | 12:12:06 | |
| 12:17:58 | |
| I realize I can still create the dir and give you the output hehehe :) | 12:18:10 | |
| not sure what I did but it started working. Some random stuff i had done was adding attic and substituters, and now I recently added myself as trusted user | 12:30:45 | |
| 20 Dec 2024 | ||
| 13:03:09 | ||
| 21 Dec 2024 | ||
| Hey all, I recently got annoyed by the lack of caching in incremental Go builds in Nix and decided to just fix it to work the way I thought it should (opt-in similar to ccache). I came up with this: https://github.com/dnr/nix-gocacheprog Let me know how it works for you! | 16:06:16 | |
In reply to @dnrix:matrix.orgNice! We are working on a similar approach with gocacheprog! https://github.com/adisbladis/gobuild.nix/ | 16:10:41 | |
| Ah, you already saw it. ^^ | 16:11:41 | |
| 22 Dec 2024 | ||
| I did.. that's a more ambitious project and a different focus. If I understand correctly, you end up with one derivation per module and the build caching is effectively at module granularity? I wanted to speed up incremental builds/tests so I wanted file-level granularity, more like ccache. Of course it's at the cost of purity, so it's only useful for development, but for that purpose it should be faster. | 00:54:53 | |
| * I did.. that's a more ambitious project and a different focus. If I understand correctly, you end up with one derivation per module and the build caching is effectively at module granularity? I wanted to speed up incremental builds/tests so I wanted package-level granularity, more like ccache. Of course it's at the cost of purity, so it's only useful for development, but for that purpose it should be faster. | 00:58:28 | |
| I think it's really two projects rolled up into one, with different goals:
| 04:29:21 | |
| I think per module granularity is probably a sweet spot, but you could go finer grained if you wanted to. | 04:29:57 | |
| That's true, per-module is probably fine for most projects. Per-package (or cache object) came out naturally from the way I shared the cache. | 11:10:45 | |
| How do you plan to coordinate writes to a shared impure cache? That's what led me to the client/server model. | 11:11:22 | |