On Tue, 2010-08-24 at 17:35 -0700, Dan Nicholson wrote: > To me, the only reason is that since you can't override the path at > runtime either, there's no way to set a custom path to the modules. > Maybe that's more of a runtime concern, though. >
A custom path for dri would be a path that is different from the path where the mesa dri drivers are installed (mesa default $libdir/dri). Would that even work and why would a system builder do that? This case would make jurisprudence in similar situations. Thanks!
signature.asc
Description: This is a digitally signed message part
_______________________________________________ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
