On Wed, 2017-10-11 at 11:57 +0200, Andreas Beckmann wrote: > On 10/11/2017 11:46 AM, Luca Boccassi wrote: > > Andreas, > > > > Long term, the only easy to maintain solution I can see (until > > there is > > proper support upstream for GLVND) would be to change the config in > > a > > postinst, depending on what package is installed. But that feels > > very > > wrong (changing config files) and very fragile. > > What do you think? > > Clear NACK for modifying conffiles. You would also need triggers to > change this if some package is installed/removed later on.
Yep fully agree. > I think primus needs two searchpatch variables (classic and glvnd) > and > needs to detect at runtime which one to use. Well, the second one > could > be "empty", since it uses system libs instead of driver dependent > ones. > How ever this runtime detection could look like. The additional problem is that the change would involve bumblebee too, since that's what sets up these paths. Given it's a non-trivial amount of work, I wonder if it's better to keep the workaround in place (assuming it doesn't cause problems) and then wait for server-side GLVND to happen? I've seen movement in the past few weeks, apparently support in Xorg is about to land: https://github.com/kbrenneman/libglvnd/commits/server-libglx-tag-data https://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-XDC17-GLVND https://www.phoronix.com/scan.php?page=news_item&px=Xorg-Server-1.20-Features https://lists.x.org/archives/xorg-devel/2017-July/054118.html -- Kind regards, Luca Boccassi
signature.asc
Description: This is a digitally signed message part
