Bug 8890

Summary: xserver's configure.ac should set CONFIGFILE to $sysconfdir/X11/xorg.conf
Product: xorg Reporter: Joshua Baergen <joshuabaergen>
Component: Server/GeneralAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED MOVED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: high    
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
1.2.99.0-fix-sysconfdir-references.patch none

Description Joshua Baergen 2006-11-04 15:57:13 UTC 
There is very little reference to $sysconfdir in the build system - with
daniels' input-hotplug additions, there are 3 references:

~/xorg/xserver $ grep sysconfdir -R *
config/Makefile.am:dbusconfigdir = $(sysconfdir)/dbus-1/system.d
configure.ac:   CONFIGFILE="$sysconfdir/$XF86CONFIGFILE"
hw/xprint/etc/Xsession.d/Makefile.am:xpcdir = $(sysconfdir)/X11/Xsession.d

Since the dbus file belongs in $sysconfdir and xprint references
$sysconfdir/X11, I think CONFIGFILE should also reference $sysconfdir/X11.
Comment 1 Joshua Baergen 2006-11-04 15:58:11 UTC 
Created attachment 7651 [details] [review]
1.2.99.0-fix-sysconfdir-references.patch

Patch that does just that.
Comment 2 Daniel Stone 2007-02-27 01:34:22 UTC 
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 3 chemtech 2013-03-15 15:08:22 UTC 
Joshua Baergen 
Do you still experience this issue with newer soft ?
Please check the status of your issue.
Comment 4 GitLab Migration User 2018-12-13 18:34:23 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/242.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.