| 14 May 2025 |
 @curid:matrix.org | What's the easiest use new manifests in an old version of rust-overlay? | 17:16:25 |
| @curid:matrix.org |
- Bump minimal supported stable nixpkgs to 23.05
https://github.com/oxalica/rust-overlay/commit/0bf05d8534406776a0fbc9ed8d4ef5bd925b056a
my nixpkgs version is older than that
| 17:17:09 |
|  kraem changed their profile picture. | 17:16:42 |
 @aloisw:julia0815.de | Bumping your nixpkgs version is not a solution I guess? | 17:17:52 |
| @curid:matrix.org | Using old version for old glibc | 17:18:41 |
| @aloisw:julia0815.de | Why do you need old glibc? | 17:19:21 |
| @curid:matrix.org | To produce portable binaries | 17:20:50 |
| @aloisw:julia0815.de | The binaries are any more or less portable when you do that, since they still rely on the glibc being in the /nix/store. If you want to build portable binaries using Nix the best choice is probably static builds with musl. | 17:21:52 |
| @curid:matrix.org | hehe patchelf --set-interpreter "/lib64/ld-linux-x86-64.so.2" "$file" | 17:22:40 |
| @curid:matrix.org | I admit that it's rather cursed, but it has worked so far | 17:23:41 |
 Alyssa Ross | Is pkgsStatic not an option? | 17:23:52 |
| @curid:matrix.org | binary uses runtime linking | 17:24:27 |
| @curid:matrix.org | * app needs runtime linking | 17:25:05 |
| @curid:matrix.org | I guess I'll vendor rust-overlay if nobody has a better idea | 17:28:35 |
 K900 | I feel like it might be a better idea to build a custom stdenv | 17:29:28 |
| K900 | With an older glibc and recent everything else | 17:29:49 |
| @curid:matrix.org | Would I need to mess with the fragile cross compilation? | 17:32:10 |
