<!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 Sun, 2011-01-09 at 11:52 -0800, Alan Coopersmith wrote: <BLOCKQUOTE TYPE=CITE> <PRE> On 01/ 8/11 06:19 PM, Gaetan Nadon wrote: > xorgconf.cpp: replaced __xconfigfile__ with xorg.conf as this file name > is hard coded in the xserver configuration and cannot change. This, and several similar defines/substitutions are leftovers from the XFree86->Xorg migration. When we first created the Xorg server from the XFree86 sources, we provided ways to build with the old file names for the server & its configuration files, log files, etc. to allow distros to switch to the new code base without having to update the rest of their code base & documentation to the new names first - their installer/configuration utilities could continue to run XFree86 and create XF86config files. </PRE> </BLOCKQUOTE> Saying "a lot of work" would be an understatement! <BLOCKQUOTE TYPE=CITE> <PRE> While I know one major distro (the one who contributed the work to use the defines to make this possible) was using this 6 years ago, I don't think anyone uses it today, and it could probably all go away, though I suppose leaving it in preserves an easier ability to fork if someday X.Org similarly falls apart as XFree86 and the X Consortia did before it. </PRE> </BLOCKQUOTE> I would normally not have touched it as it was not part of my core mission, but "__xconfigfile__" was already used in other man pages such as libXxf86vm which draws the text from util-macros MAN_SUBSTS. Even if the server would change the name, it would remain intact everywhere else. In the server man pages I would've had to deal with conflicting substitutions. Anyway I slice it, something would have to change on the next fork, but I won't be around :-) Thanks for the review, I fixed the typo multiple instances. </BODY> </HTML>