| 5 Jul 2022 |
 kraem | np :) i think you want to do buildInputs = with pkgs; [ glib ]; nativeBuildInputs = with pkgs; [ pkgconfig ] | 08:13:48 |
 deep6 | is it now just a matter of iterating through and adding the dependencies as they come up to buildInputs? | 08:20:11 |
| kraem | yeah, pretty much | 08:23:27 |
| deep6 | any idea what the gdk 3.0 package is called, tried gdk, gdk3, gdk30 and searched using search.nixos no luck | 08:25:35 |
| deep6 | or is it not packaged... you'd think it would be if gdk-pixbuf is... | 08:26:39 |
 Linux Hackerman | It's part of gtk iirc | 08:26:52 |
| deep6 | thanks, I'll give it a go | 08:28:02 |
| deep6 | managed to get this packaged up! | 08:33:58 |
| deep6 | thanks Linux Hackerman | 08:33:58 |
| deep6 | oh and thanks as well kraem | 08:42:03 |
| deep6 | sorry forgot you there earlier :) | 08:42:06 |
|  akadude left the room. | 11:59:35 |
| 6 Jul 2022 |
|  kevin joined the room. | 00:15:05 |
| kevin | What's the recommended way to package crates currently? I've used like 6 different things over the last two years lol | 00:20:46 |
|  Artturin joined the room. | 18:06:52 |
| 8 Jul 2022 |
|  biohazard6743 joined the room. | 18:06:11 |
|  David joined the room. | 20:01:07 |
| 12 Jul 2022 |
|  Janne Heß joined the room. | 07:20:08 |
| Janne Heß left the room. | 07:21:12 |
| 13 Jul 2022 |
|  pennae joined the room. | 08:17:44 |
| pennae | if we want to package a rust thing with tests that have to run the compiled binary multiple times with different sets of flags, what's the best way to do that? | 08:18:18 |
| pennae | running target/${rust.toRustTargetSpec stdenv.hostPlatform}/release/$thing doesn't seem like it's the intended solution | 08:20:01 |
 Alyssa Ross | What does upstream do? | 08:32:40 |
| pennae | it's a webservice that has a test suite for its rest api, can run in two different modes of lockdown with two different sets of tests | 08:34:36 |
| pennae | we are upstream, so all changes to make this easy are on the table | 08:34:50 |
| Alyssa Ross | Is it possible a library interface that you could pass the options to, so you don't have to run the compiled binary? | 08:36:19 |
| Alyssa Ross | Alternatively, I think cargo integration tests give you the binary path? | 08:36:39 |
| pennae | pretty much have to run the binary, part of what we're testing is how the client reacts to the responses | 08:36:42 |
| Alyssa Ross | > Binary targets are automatically built if there is an integration test. This allows an integration test to execute the binary to exercise and test its behavior. The CARGO_BIN_EXE_<name> environment variable is set when the integration test is built so that it can use the env macro to locate the executable. | 08:37:38 |
| Alyssa Ross | https://doc.rust-lang.org/cargo/reference/cargo-targets.html#integration-tests | 08:37:44 |
