| 1 Jul 2025 |
 Puna | support for POWER < 8 got dropped, and those systems are the only ones that are affordable, and where using big-endian really made sense | 09:34:11 |
 K900 | Yeeeeeeeeeeah | 09:34:51 |
 Diamond (it/she) | on a basic system i dont think theres much youd miss out, more than that it depends on what youll use it for | 21:00:09 |
| Diamond (it/she) | like a lot of web stuff are in Go for example | 21:00:17 |
| Diamond (it/she) | https://groups.google.com/g/golang-dev/c/5ZKcPsDo1fg?pli=1 | 21:01:24 |
| Diamond (it/she) | it sucks bc iant left all Go development efforts internally so this probably won't be coming anytime soon... | 21:01:43 |
| 2 Jul 2025 |
| Puna | i'm building my way from stdenv to various things necessary for an average system, so anything that's written in Go along the way. so far it's only been necessary for some optional tools in libcap, which did seem to build just fine with the compiler. | 10:39:00 |
| 3 Jul 2025 |
 jsnf | Suppose you are packaging a go project that used go version 1.24.4 ( declared in the go.mod)
Would you use BuildGoModule or BuildGo124Module?
The project will upgrade go versions according to new releases | 12:56:24 |
| jsnf | * Suppose you are packaging a go project that uses go version 1.24.4 ( declared in the go.mod)
Would you use BuildGoModule or BuildGo124Module?
The project will upgrade go versions according to new releases | 12:56:33 |
| jsnf | * Suppose you are packaging a go project that uses go version 1.24.4 ( declared in the go.mod)
Would you use BuildGoModule or BuildGo124Module?
The project will upgrade go versions according to new releases | 12:56:45 |
| jsnf | Its for nixpkgs | 12:57:27 |
 jrick | dunno the nixpkgs policy but i would only specify the version if the current version was too low | 12:57:35 |
| jsnf | So according to which go version is used in the latest release or unstable channel? | 12:58:45 |
| jrick | or maybe even patch the go.mod version... | 12:59:27 |
| jrick | i don't know if there are any hard rules about how to deal with it, but i'm sure the reviewers will give their opinions | 13:00:45 |
| jsnf | Sadly cant do that as its not my project but something im packaging for others haha | 13:00:52 |
| jsnf | Yeaa | 13:01:01 |
| jsnf | Thank you tho, preciate your help | 13:01:15 |
 Paul Meyer (katexochen) | policy documented here: https://github.com/NixOS/nixpkgs/blob/master/pkgs/build-support/go/README.md | 14:15:03 |
| Paul Meyer (katexochen) | you should use buildGoModule where ever possible (with some minor exceptions) | 14:15:34 |
| Paul Meyer (katexochen) | Shouldn't be a problem to substitute the go/toolchain version in go.mod from x.x.x to x.x.0 if needed. | 14:16:59 |
| Paul Meyer (katexochen) | There is also a section in the manual on versioned builders: https://nixos.org/manual/nixpkgs/unstable/#ssec-go-toolchain-versions | 14:18:38 |
| 5 Jul 2025 |
| jsnf | Ahhh got it, thank you so much! | 15:39:19 |
| 10 Jul 2025 |
|  @aerunakai:matrix.org joined the room. | 05:46:05 |
 nazarewk | is there a way to build system-independent Go binaries on NixOS? I'm trying to build an Alpine container that requires passing the binary externally and getting those pesky file not founds | 19:08:33 |
 Curid | why not use a scratch base instead of alpine? | 19:10:47 |
| nazarewk | could probably design it around scratch some time in the future, but right now I need to create an entrypoint bash script for the app and that's it | 19:12:08 |
| Curid | should be distro independent if you set CGO_ENABLE=0 | 19:14:08 |
| jrick | not necessarily. enabling pie will still use the dynamic loader | 19:16:24 |
| jrick | but you can override the path to the dynamic loader, and force it to use the standard path to the musl one which will work on alpine | 19:17:07 |
