| 19 Dec 2025 |
K900 | I don't know why it wants all three | 13:34:59 |
K900 | Maybe gpgme needs to propagate the other two? | 13:35:06 |
ghpzin | As I understand all these things (including qgpgme) except for libgpg-error were one and the same before that update PR. So there was never a question of propagating, it was just a bundle with all cmake .pc files and everything together. | 13:37:06 |
ghpzin | As I understand all these things (including qgpgme) except for libgpg-error were one and the same before that update PR. So there was never a question of propagating, it was just a bundle with all cmake, .pc files and everything together. Not sure how person doing that PR decided on how split should work. | 13:37:44 |
K900 | @dotlambda thoughts? | 13:38:19 |
ghpzin | As I understand all these things (including qgpgme that added qt things on top) except for libgpg-error were one and the same before that update PR. So there was never a question of propagating, it was just a bundle with all cmake, .pc files and everything together. Not sure how person doing that PR decided on how split should work. | 14:02:46 |
dotlambda | If other packages build fine, I think that's proof that qgpgme shouldn't propagate gpgme(pp) | 14:03:48 |
K900 | I guess | 14:06:33 |
| @mtvkxsw9tngk:matrix.org left the room. | 14:17:26 |
dotlambda | Actually, gpgmepp should probably propagate gpgme and libgpg-error as /nix/store/iixl4y6ddcvh73iihfrng1wg8v2r07jp-gpgmepp-2.0.0/lib/cmake/Gpgmepp/GpgmeppConfig.cmake contains
find_dependency(LibGpgError "1.47")
find_dependency(Gpgme "2.0.0")
| 14:59:31 |
dotlambda | And qgpgme should propagate gpgmepp.
fixed in https://github.com/NixOS/nixpkgs/pull/472418
Sorry for messing up! | 15:19:40 |
K900 | Is that enough to get libkleo building? | 15:20:16 |
K900 | (genuine question I am still very migraine) | 15:20:27 |
dotlambda | yes, it will get gpgme and libgpg-error transitively | 15:21:22 |
K900 | OK cool | 15:21:28 |
K900 | Feel free to merge when you're done then | 15:21:38 |
ghpzin | Built my plasma6 config from staging-next with it, seems to work. | 15:38:49 |
dotlambda | How do I make zug use gcc 14, but only if the stdenv uses gcc anyway?
https://github.com/arximboldi/zug/issues/45 | 16:49:53 |
K900 | Patch it instead? | 16:50:35 |
dotlambda | There's no upstream patch | 16:51:06 |
K900 | I mean it tells you what to change | 16:51:17 |
dotlambda | In the issue they discuss that replacing impl with impl_ causes other problems | 16:52:24 |
K900 | Well the other problem is | 16:53:18 |
K900 | That thing seems to be mostly headers | 16:53:22 |
K900 | So even if you give it a different stdenv anything including it will still explode | 16:53:33 |
dotlambda | true | 16:53:43 |
K900 | Also my C++ is very rusty (hehe) but I think that last comment is correct? | 16:53:47 |
dotlambda | I guess I'll give it a try | 16:54:19 |
ghpzin | You could also -Wno-error=template-body, not sure if that would be better or worse. | 17:08:57 |
ghpzin | You could also -Wno-error=template-body, not sure if that would be better or worse. Kind of surprised no other distro patches/works around it somehow, considering they should have packaged krita | 17:09:52 |