<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0"> </HEAD> <BODY> On Tue, 2010-08-24 at 17:35 -0700, Dan Nicholson wrote: <BLOCKQUOTE TYPE=CITE> <TT>To me, the only reason is that since you can't override the path at</TT> <TT>runtime either, there's no way to set a custom path to the modules.</TT> <TT>Maybe that's more of a runtime concern, though.</TT> </BLOCKQUOTE> 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! </BODY> </HTML>