13:43 <ifreund> 2 bugs left...

13:50 <novakane> good luck with that, can't help with these ones... are you able to replicate the high cpu usage with the mouse on background?

13:51 <ifreund> haven't tried yet

14:01 <novakane> huh tried to launch an other instance of river in an other tty and my current session crashed

14:05 <ifreund> novakane: run `xi seatd` and restart

14:06 <ifreund> https://github.com/swaywm/wlroots/issues/3200

14:06 <ifreund> void recently updated to the libinput version where things started breaking

14:08 <novakane> ifreund: oh nice thanks!

14:08 <zdykstra1> ifreund: do you have a template to package up river git head? I'd like to try it, but I prefer having xbps track what's installed.

14:09 <ifreund> zdykstra1: I haven't made one yet, if you're interested in trying yourself it should look pretty much the same as the one for rundird here but with submodules: https://github.com/void-linux/void-packages/pull/29288

14:10 <ifreund> I will of course package river for void once I fix the last 2 open bugs and tag a release

14:10 <zdykstra1> *nod*

14:13 <ifreund> the complexity in the zig build style is all for cross compilation, if you don't care about that a simple `zig build -Dxwayland --prefix /usr` would suffice

14:13 <ifreund> -Drelease-safe as well if you want an optimized build

14:15 <novakane> oh I always use a command from my history to build river, and I have just realised that I always build it in debug mode

14:16 <novakane> never used -Drealease-safe for river

23:22 <drowning> a probably stupid question

23:22 <drowning> i built river locally, now trying to build rivercarro

23:22 <drowning> but rivercarro build gives up with

23:22 <drowning> pkg-config --variable=pkgdatadir river-protocols

23:22 <drowning> error: the following build command failed with exit code 1:

23:29 <leon-p> drowning: seems like when you installed river, you did not install rivers protocol extensions. These are not necessary for river itself to function, but they are build-time dependencies for programs that want to communicate with river using those specialised interfaces.

23:33 <ifreund> drowning: if you installed river to ~/.local, you'd need to set PKG_CONFIG_PATH for pkg-config to find the installed protocols

23:33 <drowning> i see

23:36 <ifreund> sadly I don't know of a better way than using pkg-config to do this kind of thing, maybe just having everyone vendor the protocols they need as is the norm for wlr-protocols is better

23:40 <drowning> "export PKG_CONFIG_PATH=~/.local/share/"?

23:40 <drowning> a river-protocols folder is in there

23:40 <drowning> but it gives up still

23:47 <ifreund> drowning: you'd need ~/.local/share/pkgconfig I believe

23:48 <drowning> it worked! thank you.