jaeger changed the topic of #crux-devel to: CRUX (https://crux.nu/) development channel | Logs: https://libera.irclog.whitequark.org/crux-devel/
ivandi has quit [Quit: WeeChat 3.4]
ivandi has joined #crux-devel
mbarbar has quit [*.net *.split]
farkuhar has left #crux-devel [#crux-devel]
SiFuh_ has joined #crux-devel
SiFuh has quit [Ping timeout: 260 seconds]
mbarbar has joined #crux-devel
SiFuh_ has quit [Ping timeout: 240 seconds]
SiFuh has joined #crux-devel
farkuhar has joined #crux-devel
groovy2shoes has quit [Ping timeout: 240 seconds]
groovy2shoes has joined #crux-devel
ivandi has quit [Quit: WeeChat 3.4]
ivandi has joined #crux-devel
<farkuhar> I'm having trouble identifying which port in the xorg collection is responsible for creating /var/lib/xkb. The meson setup command in the xorg-server Pkgfile refers to this directory, and the xkeyboard-config build script makes a symlink to this directory, but no port actually has var/lib/xkb in its footprint!
<farkuhar> And if /var/lib/xkb is supposed to be created at runtime when X is first launched, how can we be sure that the user has the necessary permissions to create a directory in /var/lib? A user in the video and input groups, running stenur's startx script, would not have the escalated privileges of the setuid Xorg.wrap binary.
<groovy2shoes> $ ls /var/lib/xkb
<groovy2shoes> ls: cannot access '/var/lib/xkb': No such file or directory
<groovy2shoes> definitely running X
<SiFuh> You'll probably find a desktop environment is creating it
<farkuhar> actually I think the xorg-server footprint changed when the build system switched to meson: https://lists.crux.nu/pipermail/crux/2021-September/006979.html
<farkuhar> ... and no port subsequently volunteered to handle the creation of /var/lib/xkb
<SiFuh> farkuhar: possible, what is the time stamp of that actual directory?
<farkuhar> SiFuh: just like groovy2shoes, the directory doesn't exist on my system. The first time I built xorg-server on this machine was after the switch to meson.
<farkuhar> The absence of the directory is not fatal to the server. I wouldn't have noticed it except that the broken symlink showed up in a routine filesystem scan.
<SiFuh> Didn't answer my question but I will check my older back ups
<SiFuh> farkuhar: you are 100% correct
<SiFuh> My 2021 10 26 backup doesn't have it but every backup before has it