mesa DRI drivers path
by 414N from LinuxQuestions.org on (#5BGK4)
Greetings,
while discussing a Steam-runtime issue on GitHub, it came to light that Slackware uses what is, for today distros "standard", an unconventional path for DRI drivers, e.g "/usr/lib${LIBDIRSUFFIX}/xorg/modules/dri".
This setting is enforced in past and current mesa.SlackBuild scripts with an explicit option ("-Ddri-drivers-path=/usr/lib${LIBDIRSUFFIX}/xorg/modules/dri") but is there a reason for putting DRI drivers there instead of "/usr/lib${LIBDIRSUFFIX}/dri", where VA-API drivers are already put by the same mesa package?
while discussing a Steam-runtime issue on GitHub, it came to light that Slackware uses what is, for today distros "standard", an unconventional path for DRI drivers, e.g "/usr/lib${LIBDIRSUFFIX}/xorg/modules/dri".
This setting is enforced in past and current mesa.SlackBuild scripts with an explicit option ("-Ddri-drivers-path=/usr/lib${LIBDIRSUFFIX}/xorg/modules/dri") but is there a reason for putting DRI drivers there instead of "/usr/lib${LIBDIRSUFFIX}/dri", where VA-API drivers are already put by the same mesa package?