<nee`>The murmur service is comming along well. I tested voice chat, text chat, and registering the server in the public server list today. I will probably send a patch in a few days, after I tested the other options.
<atw>nice! How difficult is it to write a service? I might want to do one at some point
<nee`>atw: Not very difficult in itself. But I find it to be a lot of work to get informed on all the options of a software and to write documentation.
<atw>and then codify those options as options to the service procedure? Yeah, that does sound tough...
<atw>Kinda means that services form a universal configuration language, right?
<ngz>rekado_: Oddly, at the same location in store, i.e, /gnu/store/...-qttools-5.9.2/lib/cmake/, Qt5UiTools/ provides Qt5UiToolsConfigVersion.cmake, which contains a version string. Qt5LinguistTools/ doesn't provide one.
<efraim>It also happened for owncloud-client and I believe quassel
<htgoebel>If I need an input native and propagated, can I list it twice?
<ngz>Other distributions (in particular NixOS) do not do anything special about Qt5linguisttools. Very strange.
<iyzsong>Oh, linguist.pro search ConfigVersion.cmake.in in 'QT_HOST_DATA/src', which point to the wrong place by qt.conf in the 'configure-qmake'. I'll fix it soon...
<htgoebel>Which means: libkdeinit5_kcminit_startup.so will be load
<htgoebel>Looks like I need to ask for assistance on the mailinglist
<htgoebel>For developing the patch I need to work in kinit, but for testing the patch, I need to set up a full KDE Plasma environment with many packages depending on kinit. So every change-cycle will take half an hour (and more). How can I work around this? E.g. by using grafts?
<efraim>I don't remember the flag, but guix build --help should show you the custom graft flag