| 3 Aug 2021 |
 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 |
| pamplemousse | In reply to @tomberek:matrix.org
hrm.... pkgconfig is usually pretty good at finding those things... are you using this in a downstream build? yes, I am trying to use it to build fuzzers for nix | 20:27:25 |
| pamplemousse | In reply to @qyliss:fairydust.space
should be lib/pkgconfig, shouldn't it? got the same problem for both | 20:34:22 |
|  fzakaria joined the room. | 21:34:07 |
| fzakaria | Just noticed this channel.
Wouldn't mind discussing https://github.com/NixOS/nix/issues/5092 with someone that might have some insight | 21:34:24 |
| fzakaria | Trying to get some context to work on a fix | 21:34:37 |
| 5 Aug 2021 |
 John Ericson | does the store-specific options not get put in the manual yet? | 17:38:15 |
| John Ericson | * do the store-specific options not get put in the manual yet? | 17:38:20 |
 Regnat | No, I don’t think they are. They are only available with nix describe-stores | 20:32:40 |
| 6 Aug 2021 |
|  Rev. CornWallace III (novus ordo seclorum) changed their display name from continuouswave to cw (? days since last shower). | 18:10:47 |
|  Robert Hensing (roberth) changed their display name from roberth to Robert Hensing (roberth). | 19:46:50 |
|  ash (it/its) 🏳️⚧️ changed their display name from ashkitten (it/its) 🏳️⚧️ to kity. | 21:02:52 |
| ash (it/its) 🏳️⚧️ changed their display name from kity to ash (it/its). | 21:03:40 |
| ash (it/its) 🏳️⚧️ changed their display name from ash (it/its) to ash (it/its) 🏳️⚧️. | 21:04:53 |
| fzakaria | Small fix for the issue i filed above | 22:37:17 |
| fzakaria | https://github.com/NixOS/nix/pull/5101 | 22:37:18 |
| tomberek | In reply to @theophane:hufschmitt.net
No, I don’t think they are. They are only available with nix describe-stores I’ve always found myself going through the code to find them. Wasn’t aware of this command. Thanks! | 23:00:41 |
| 7 Aug 2021 |
 balsoft | https://github.com/NixOS/nix/pull/5102 is a very simple change, but it empowers us to use nixConfig.flake-registry for automatically keeping input versions up to date. It should be safe. | 11:44:33 |
| tomberek | balsoft: this changes the concept of a registry a bit. How would this work when a flake depends on another? or "follows"? What if they depend on different flakes? | 18:31:20 |
| tomberek | * balsoft: this changes the concept of a registry a bit. How would this work when a flake depends on another? or "follows"? What if they depend on different registries? | 18:31:50 |
| balsoft | In reply to @tomberek:matrix.org
balsoft: this changes the concept of a registry a bit. How would this work when a flake depends on another? or "follows"? What if they depend on different registries? No, it doesn't change the concept of anything. Only top-level flake registry matters | 19:57:31 |
| balsoft | * Only top-level flake nixConfig gets applied | 19:57:39 |
