| 18 May 2025 |
|  @sneid:matrix.org left the room. | 10:34:33 |
|  Makuru joined the room. | 11:10:30 |
| Makuru | Is it possible to make rust builds with cargo, reproducible?
So that I get the exact same binary? | 11:13:02 |
 Alyssa Ross | what are you finding not to be reproducible? | 11:13:28 |
| Makuru | I haven't tested it yet but are there compiler flags or whatever I need to make a nix build reproducible? | 11:14:16 |
| Alyssa Ross | Generally we aim for reproducibility by default, but can't guarantee it, so you'll have to test to make sure. | 11:14:46 |
| Makuru | Also, can I make my flake check the output? Should I make a post install hook? | 11:16:25 |
 K900 | What do you mean by "check the output"? | 11:17:02 |
| Makuru | In reply to @k900:0upti.me
What do you mean by "check the output"? I mean to test it with a checksum. | 11:18:38 |
| Makuru | So others know that the build worked. | 11:18:57 |
| K900 | Uhh would not recommend | 11:19:09 |
| K900 | Unless you want to update that checksum every time | 11:19:18 |
| K900 | For every architecture | 11:19:22 |
| Makuru | It should error, if the flake output is not the same. | 11:19:24 |
| Makuru | In reply to @k900:0upti.me
For every architecture Oh yeah, oof. | 11:19:31 |
| K900 | And your source for the checksum is "trust me bro" anyway | 11:19:32 |
| K900 | Like, the purpose of reproducible builds is for others to verify that the binary they downloaded corresponds to the source | 11:20:09 |
| Makuru | Yeah | 11:20:18 |
| K900 | If you don't publish binaries, it doesn't do anything | 11:20:19 |
| K900 | And if you do, you don't need a checksum | 11:20:26 |
| Makuru | I guess, it could be useful to have the checksum from a secondary source, besides nixpkgs. | 11:20:57 |
| 19 May 2025 |
| Makuru | Does anyone know here, how to set arbitrary env vars with crane? | 20:18:36 |
|  oak 🏳️🌈♥️ changed their display name from oak 🫱⭕🫲 to oak. | 10:58:20 |
| oak 🏳️🌈♥️ changed their display name from oak to oak 🏳️🌈♥️. | 11:00:30 |
| 21 May 2025 |
|  WeetHet changed their profile picture. | 10:59:08 |
|  oddlama changed their display name from Malte to oddlama. | 17:42:00 |
|  @michael.zeagler:matrix.org joined the room. | 19:15:40 |
|  @bloxx12:matrix.org left the room. | 21:30:01 |
| 22 May 2025 |
 Toma | I'm mostly happy with fetchCargoVendor, though I worry about the impact on the cache:
every time a dependency of fetchCargoVendor changes, the non-FOD part needs to be re-cached, which can accumulate, and take up quite a lot of storage.
I wish there was a way to force hydra to not cache certain packages.
There is meta.hydraPlatforms = [], but AIUI it would only disable building it if it was directly built by hydra, but since it's a dependency of a package that is not disabled on hydra, it will get built and cached anyway...
I guess this could also be handled by content-addressed derivations...
Note: there are >2000 rust-based packages in nixpkgs currently
Question 1: What do you all think, how bad is this problem?
Question 2: How does one check how much storage a certain derivation takes up cached?
| 00:15:18 |
 emily | you can fetch the NAR | 09:00:12 |
