| 28 Jan 2024 |
 Paul Meyer (katexochen) | Draft for the go list thing: https://github.com/NixOS/nixpkgs/pull/284568 | 16:39:48 |
| 31 Jan 2024 |
|  Federico Damián Schonborn changed their profile picture. | 03:36:40 |
| Federico Damián Schonborn changed their profile picture. | 06:22:16 |
| 6 Feb 2024 |
 @qbit:tapenet.org | the other bummer about our build for go stuff is that we can't take advantage of a global build cache | 15:26:06 |
| @qbit:tapenet.org | i don't know how it possibly could... just a bummer for speed | 15:27:23 |
| Paul Meyer (katexochen) | Well, I think the way Bazel handles this is by not using the higher level go "build" command but the lower level commands to build each package in separate to get a linkable archive, then invoke the linker on those archives when building the final binary. | 15:47:09 |
| @qbit:tapenet.org | interesting | 16:23:44 |
| Paul Meyer (katexochen) | https://github.com/bazelbuild/rules_go/blob/07317c7ce2ae6e6cda269c0c3ec7eac171363936/go/tools/builders/compilepkg.go#L538-L560 | 16:34:07 |
|  Moritz Sanft set a profile picture. | 17:17:54 |
 Sandro 🐧 | Bazel also thought it would be a good idea to vendor all kinds of libraries and copy their build systems... | 17:40:41 |
| Sandro 🐧 | and fetch archives against GitHub recommendations in the docs and completely breaking when they updated git-archive | 17:41:17 |
| Paul Meyer (katexochen) | Sandro 🐧: not sure how that is related to their mechanism of building Go code. | 18:12:52 |
| Paul Meyer (katexochen) | I think if you really want to break up Go builds into multiple derivations (which is nothing I propose here), the Bazel approach sounds more reasonable and correct to me than somehow injecting build cache. | 18:16:15 |
| 8 Feb 2024 |
|  symys joined the room. | 18:50:55 |
| 10 Feb 2024 |
|  anthr76 joined the room. | 14:32:02 |
| anthr76 | Hi All! I have a question. I'm trying to build some internal private go projects in nix for my teammates. Is anyone able to point me on how to pass a ~/.netrc to the nix build sandbox? I'm using buildGoModule | 14:34:50 |
| @qbit:tapenet.org | You’d probably need to make it during post patch or similar phase.. but you won’t have network access | 17:12:47 |
| 12 Feb 2024 |
|  lunchtime joined the room. | 02:13:35 |
| lunchtime joined the room. | 10:46:21 |
| 13 Feb 2024 |
| anthr76 | In reply to @qbit:tapenet.org
You’d probably need to make it during post patch or similar phase.. but you won’t have network access Do you have an example or bit of documentation? | 18:54:28 |
| @qbit:tapenet.org | https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#tested-using-sandboxing | 18:56:39 |
| @qbit:tapenet.org | fo rthe sandbox info | 18:56:46 |
| anthr76 | Also an option can be vendoring when it's pulling down the source tarball | 18:58:06 |
| anthr76 | but I'm not sure that's even possible | 18:58:13 |
| @qbit:tapenet.org | for the postPatch you could just do : export HOME=$(mktemp -d); cd $HOME; echo some netrc string > .netrc | 18:58:20 |
| @qbit:tapenet.org | anthr76: is this all go deps? | 18:58:36 |
| anthr76 | Yes it is | 18:58:44 |
| @qbit:tapenet.org | buildGoModule does vendoring of any deps and what not | 18:58:52 |
| @qbit:tapenet.org | vendorHash | 18:59:02 |
| @qbit:tapenet.org | grep -r buildGoModule in nixpkgs and you will find plenty of examples | 19:00:40 |
