| 2 Aug 2021 |
 manveru | https://github.com/NixOS/nix/pull/5082 | 11:53:52 |
| manveru | Eelco Dolstra: would be nice if you could take a look at this :) | 11:54:10 |
| manveru | thanks a lot! | 14:34:17 |
 pamplemousse | Is the daemon protocol documented somewhere? | 21:12:49 |
 tomberek | not well last time I tried to interpret it. also see: https://github.com/NixOS/nix/issues/4655 | 21:14:03 |
 andi- | In reply to @pamplemouss_:matrix.org
Is the daemon protocol documented somewhere? It is not documented AFAIK. It isn't hard to implement just tedious. | 21:29:53 |
| andi- | If you can read haskell there is this: https://github.com/haskell-nix/hnix-store/blob/master/hnix-store-remote/src/System/Nix/Store/Remote.hs | 21:31:13 |
| andi- | otherwise just read the C++ code | 21:31:19 |
| pamplemousse | In reply to @andi:kack.it
otherwise just read the C++ code ^^
That's what I was doing, but eventually, I wondered if there was a spec at all | 21:38:22 |
| andi- | What are you working on? | 21:38:36 |
| pamplemousse | As part of https://discourse.nixos.org/t/tweag-fellowship-fuzzing-nix-0, I am at a point where I want to target the daemon. | 21:39:50 |
| andi- | Neat. I've some rust code that exposes most of the store operations via commands... Code isn't public yet but I wanted to do that as well | 21:40:33 |
| pamplemousse | Problem is, if I only send random data, it will take a while to mutate to discover new paths.
Also, if I only send structured input, I might miss some interesting errors (especially as there is no spec / everything is hand made). | 21:41:31 |
| 3 Aug 2021 |
|  Gytis Ivaskevicius joined the room. | 10:10:15 |
| Gytis Ivaskevicius | Pls review 🥺 👉️👈️
Mines:
https://github.com/NixOS/nix/pull/4914
Friends:
https://github.com/NixOS/nix/pull/4641
https://github.com/NixOS/nix/pull/4765 | 10:10:22 |
| Gytis Ivaskevicius | (at this point I am being redirected from one channel to another just to get a review 😀 ) | 10:11:11 |
| manveru | Eelco Dolstra: is there anything else needed for https://github.com/NixOS/nix/pull/4895 to get merged as well? | 10:32:43 |
 roberth | I will refrain from writing a rant about incremental fixes not getting merged | 11:25:50 |
| roberth | please merge manveru 's pr | 11:26:18 |
| pamplemousse | I am trying to add a library to the flake.nix of nix, but it does not seem to be picked up by pkgconfig... | 22:00:22 |
| pamplemousse | I am trying to add libprotobuf-mutator for which I made https://github.com/NixOS/nixpkgs/pull/132488
and I edited the flake.nix to point inputs.nixpkgs.url to a path:/ where my nixpkgs clone lives | 22:01:14 |
| pamplemousse | (I am not particularly attached to pkgconfig, but it seems to be what meson uses to see where are the required libraries | 22:02:06 |
| pamplemousse | * (I am not particularly attached to pkgconfig, but it seems to be what meson uses to see where are the required libraries) | 22:02:11 |
| 4 Aug 2021 |
| tomberek | pamplemousse: does your package produce a .pc? | 01:45:58 |
| pamplemousse | @tomberek Yes: share/pkgconfig/protobuf-mutator.pc . | 15:59:13 |
| pamplemousse | * tomberek: Yes: share/pkgconfig/protobuf-mutator.pc . | 15:59:33 |
| tomberek | hrm.... pkgconfig is usually pretty good at finding those things... are you using this in a downstream build? | 18:50:48 |
 Alyssa Ross | should be lib/pkgconfig, shouldn't it? | 19:23:07 |
 Vladimír Čunát | Both are OK IIRC. | 19:58:43 |
| Vladimír Čunát | There are commonly issues with broken paths written inside *.pc. | 19:59:35 |
