15:48 <Guest3> hey how can I start retroarch in River? it works in xfce, can i force xwayland somehow?

15:59 <LarstiQ> Guest3: what is retroarch?

16:01 <Guest3> Gameemulation management tool

16:02 <LarstiQ> if it's just a program then start it like any other? If it needs xwayland make sure your river is compiled with support

16:02 <Guest3> I installed it via pacman, so it should be included?

16:15 <LarstiQ> probably, but I don't know how your distro has packaged it

16:43 <Guest3> https://archlinux.org/packages/extra/x86_64/river/

16:43 <Guest3> it is included

17:04 <ifreund> Guest3: what error message are you getting?

17:07 <Guest3> None, so maybe it start but it is somehow hidden

17:11 <Guest3> Thanks I figured it out, seems to be a problem with retroarch

21:14 <Guest3> Retroarch started after some time, maybe 20 seconds, in River and I could play a race of F-Zero. Next time it does not start in 5 minutes and there is no option to see what it is actually doing (at least not on the man page). Now it is not even starting in XFCE for who knows why. I think I will just use an N64 emulator directly and ditch it.

21:32 <Guest3> There is an alternative frontend for libretro named ludo that is written in Go that I'm currently installing. It seems that I'm not the only one with weird loading behavior of retroarch seemingly out of nowhere

21:36 <ifreund> check that out, got rid of the git submodules for waylock on the next-zig branch: https://codeberg.org/ifreund/waylock/commit/0c7643f3c068a7f1e065b16ac1b0094ef16fc3f4

21:36 <ifreund> still need to test the new --system packaging mode

22:42 <adamcstephens> neat! happy to see that work in zig and look forward to updating the nix package :)

23:10 <alebastr> ifreund: this change makes me slightly apprehensive. like 'packaging different git snapshots of the same dependency to be able to build both x and y' apprehensive

23:18 <adamcstephens> how is this any different than every distribution which packages common C libraries for dynamic linking?