| 29 Mar 2026 |
 emily | I'm much more concerned about mrustc's ability to keep up with both LLVM and Rust than about a few extra hours of bootstrap | 21:02:39 |
 whispers [& it/fae] | Redacted or Malformed Event | 21:05:06 |
| whispers [& it/fae] | Redacted or Malformed Event | 21:06:11 |
| whispers [& it/fae] | * | 21:06:22 |
| whispers [& it/fae] | * | 21:06:33 |
| whispers [& it/fae] | * | 21:07:23 |
| whispers [& it/fae] | * the fact that, had we been doing this before mrustc 0.12, this would've been 10 hours of building rust compilers on our laptop to get up to stable makes that effectively impossible, and mrustc is a one person project that has a very hard job so it's very likely to lag | 21:07:36 |
| 30 Mar 2026 |
 Charles | is there a way to tell buildRustPackage to only include one of the binaries in the output in a workspace with multiple binaries? | 01:58:00 |
| Charles | i could just rm in postInstall but like, they don't need to be built in the first place | 02:00:02 |
| Charles | okay, buildAndTestSubdir works | 02:02:15 |
 eveeifyeve | Charles: You could specify to build a specific package only. | 03:05:57 |
| Charles | i know about the --package option but it wasn't clear to me if there was an intended way to pass that to cargo while using buildRustPackage | 03:06:32 |
| eveeifyeve | * Charles: You could specify to build a specific package. | 03:06:34 |
| Charles | and also that message is pretty much free of information | 03:06:53 |
| eveeifyeve | It's intended way to parse it if you want to build a specific package. Note you must also do it for the test phase as well. | 03:07:36 |
 dish [Fox/It/She] | I believe buildAndTestSubdir is the intended way to build a single binary | 03:08:14 |
| Charles | so my question kinda implies that i know that cargo can do this on its own, in addition to explicitly asking how to do this in the context of buildRustPackage. how do you suggest i do what you are telling me to do, precisely, in terms of, say, some example nix code? | 03:09:18 |
| eveeifyeve | cargoBuildFlags = [ "--package <package>" ]; & cargoTestFlags = [ "--package <package>" ];? | 03:10:57 |
| eveeifyeve | But also the suggestion from dish [Fox/It/She] works as well. | 03:11:37 |
| Charles | okay, so maybe just lead with that next time instead of basically repeating my question back at me | 03:11:36 |
| Charles | should i elaborate/rephrase? | 03:14:26 |
|  @alto:private.coffee left the room. | 13:39:37 |
| 31 Mar 2026 |
|  raf joined the room. | 11:22:18 |
|  ryo changed their profile picture. | 13:16:33 |
| 1 Apr 2026 |
 azban | This package's build scripts clones a repo to the OUT_DIR https://github.com/isar-community/isar-community/blob/4c2cd02d4e5c17b7edca89d141d1729ddc1698ff/packages/mdbx_sys/build.rs#L60-L62
Is there a clever way to do this? All that I can think of is to copy the files, set an env var that specifies that directory, and add a patch to not clone the repo, and to look for that env var. | 01:00:55 |
|  Azad Satkarni changed their display name from 7karni to Azad Satkarni. | 06:40:38 |
 Alyssa Ross | Send them a PR to do something better | 06:46:37 |
| Alyssa Ross | Generally with a -sys crate it's a good idea to have some way to provide an already-compiled library so it can be built with whatever options the packaging system likes to use. | 06:47:49 |
| Alyssa Ross | You can demonstrate this if upstream is unaware by pointing to any of the popular -sys crates. | 06:48:06 |
|  @onur-ozkan:matrix.org left the room. | 08:18:11 |
