| 30 Mar 2026 |
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 |
| 3 Apr 2026 |
| @mkapra:kapra.de left the room. | 16:47:20 |
| 5 Apr 2026 |
| ritiek changed their profile picture. | 01:17:52 |
| 8 Apr 2026 |
mach50 | general rust question.
what would be a proper way to store my app configs in a human redable format, and which format should i pick? | 03:21:15 |
Charles ⚡️ | User programs: xdg base dirs spec
System programs: take a command line argument of the path to the config file
For formats, maybe have a look at KDL, it's neat | 03:23:55 |
Ralith | is that alive again? last I heard the maintainer crashed out after setting up a harassment campaign against AI users | 03:34:06 |
Ralith | often folks default to toml because it's not too weird and Rust has good tools for it | 03:34:53 |
aphasic | corn is very nixlike | 04:18:25 |
aphasic | https://cornlang.dev/ | 04:18:46 |
aphasic | i like it | 04:18:50 |
aphasic | no actual nix generator though 😅 | 04:19:23 |
aphasic | ime kdl is kind of a mess and maps horrendously from nix | 04:19:30 |
aphasic | not that there isn't code to do kdl->nix, there is, but you have to more or less manually serialise with it because their syntax and features are so disparate | 04:20:24 |
aphasic | * not that there isn't code to do nix->kdl, there is, but you have to more or less manually serialise with it because their syntax and features are so disparate | 04:20:40 |
Marien Zwart | If your audience is not nix users, a boring format like TOML is usually better (and if your audience is nix users maybe don't use kdl, I don't know exactly why but there's a home-manager module (for niri) stuck on essentially "the kdl generator is not good enough")) | 04:21:45 |
Marien Zwart | * If your audience is not nix users, a boring format like TOML is usually better (and if your audience is nix users maybe don't use kdl, I don't know exactly why but there's a home-manager module (for niri) stuck on essentially "the kdl generator is not good enough") | 04:22:09 |