| 17 Oct 2024 |
 K900 | There is a flag for it IIRC | 06:05:34 |
 Toma | Going back to what I talked about yesterday, I realize now that still requiring outputHashes would no longer be required, assuming that the sha-revision of the git repository is a good enough for reproducible output.
This new fetcher would essentially just be an alternative implementation of the vendoring logic, but written by us (just like with importCargoLock), meaning that upstream can't mess up our hashes.
Is my assumption correct? | 10:47:23 |
| Toma | * Going back to what I talked about yesterday, I realize now that still requiring outputHashes would no longer be required, assuming that the sha-revision of the git repository is good enough for reproducible output.
This new fetcher would essentially just be an alternative implementation of the vendoring logic, but written by us (just like with importCargoLock), meaning that upstream can't mess up our hashes.
Is my assumption correct? | 11:11:14 |
 tgunnoe | Has anyone seen this error before? I think -sys crates usually fail at building due to local system deps missing right
= note: ld: library not found for -liconv
clang-16: error: linker command failed with exit code 1 (use -v to see invocation)
error: could not compile `zstd-sys` (build script) due to 1 previous error
| 15:32:24 |
| tgunnoe | * Has anyone seen this error before? I think -sys crates usually fail at building due to local system deps missing right
= note: ld: library not found for -liconv
clang-16: error: linker command failed with exit code 1 (use -v to see invocation)
error: could not compile `zstd-sys` (build script) due to 1 previous error
on macOS anyways
| 15:33:07 |
 emily | you need libiconv in buildInputs for approximately 1 to 2 more weeks | 15:36:40 |
| tgunnoe | interesting. thank you | 15:38:01 |
 Alyssa Ross | Does the new Darwin stuff build libiconv into libc? | 15:39:56 |
| K900 | Into stdenv | 15:43:25 |
| K900 | Well technically into the SDKs I think | 15:43:37 |
| K900 | But you get an SDK with the stdenv so | 15:43:42 |
| emily | yeah it's not part of libc but you get it free with the purchase of any SDK | 15:50:52 |
| K900 | @Alyssa Ross @aloisw:kde.org so thoughts on the linux-firmware abomination | 15:53:03 |
| Alyssa Ross | seems fine, but not sure what it has to do with Rust :P | 16:06:07 |
| K900 | Ugh | 16:10:16 |
| tgunnoe | Redacted or Malformed Event | 17:28:33 |
|  bendlas changed their profile picture. | 17:37:47 |
| Toma | created a PR with the custom vendoring logic: https://github.com/NixOS/nixpkgs/pull/349360
it should work in most cases, but I haven't implemented a way to use other registries nor sparse dependencies, though these are rare | 21:36:27 |
| 18 Oct 2024 |
| emily | In reply to @emilazy:matrix.org
this may cause havoc for us soon: https://github.com/rust-lang/rust/pull/129687 not sure if this is in 1.82 | 00:30:14 |
| emily | but looks like we might have to deal with it soon | 00:30:23 |
|  Sammy (It/Its) left the room. | 08:39:10 |
| 19 Oct 2024 |
|  Li-ion changed their display name from ion to Li-ion. | 08:12:17 |
|  Rayan Nakib (ريان نقيب) joined the room. | 08:14:16 |
|  jwillikers joined the room. | 12:07:14 |
|  mwoodpatrickmx joined the room. | 16:54:35 |
 steveej | what crate is best suited to iterate over a nix attrset in rust? | 20:20:16 |
| K900 | Dump your attrset to JSON | 20:20:39 |
| K900 | And then use any JSON librqry | 20:20:47 |
| K900 | * And then use any JSON library | 20:20:55 |
| K900 | Actually evaluating Nix in Rust correctly is an open problem | 20:21:07 |
