On Tue, 7 Aug 2007, Johnny C. Lam wrote:

> Matthias Scheler wrote:
> > 
> > I've switched one of my systems from X.org 6.9 to modular X.org yesterday.
> > One of the things I noticed was that the new X server immediately picked
> > up existing configuration files in "/etc/X11".
> > 
> > Although this was useful behavior on that point of time it is IMHO not the
> > correct behaviour. It seems that modular X.org doesn't pay any attention
> > to "${PKG_SYSCONFDIR}" at all. Do we have a strategy for this?
> 
> Your observation about /etc/X11 and modular-xorg-server is correct.  I took a
> look at the code last night because the Xorg server wasn't picking up my
> xorg.conf file in my PKG_SYSCONFBASE=/etc/pkg.  It turns out the server itself
> ignores any --sysconfdir directive passed to the configure script (which we
> don't pass anyway) and hardcodes the following locations to find its
> configuration file:
> 
> 	/etc/X11/xorg.conf
> 	/etc/xorg.conf
> 	${X11BASE}/etc/X11/xorg.conf
> 	${X11BASE}/etc/xorg.conf
> 	${X11BASE}/lib/...

To me it looks like an error in configure.ac. It defines:
        XF86CONFIGFILE="xorg.conf"
        CONFIGFILE="$sysconfdir/$XF86CONFIGFILE"

But CONFIGFILE is never used again and is not used with AC_DEFINE_DIR for 
example. (Or maybe I missed something.)


> I'm considering putting ${sysconfdir} at the head of this list so that these
> standard locations can be used as fallbacks.
> 
> I expect there will be several other modular X.org packages that will need
> similar treatment.
> 
> Thoughts?



  Jeremy C. Reed