On Sat Jun 25 11:28:06 PDT 2011, Jeremy Huddleston wrote:
>On Jun 25, 2011, at 11:09, Dave Ray wrote:
>
>> I am creating a pkg installer which includes a custom ~/.xinitrc file on the 
>> target machine.
>
>Don't do that!  Use ~/.xinitrc.d scripts

Ok, fine, I can do that. Will the dialog go away of I do that?

FYI, I am using this startup script  to set the window manager to be something 
other than quartz-wm.

Just so I can improve my understanding, if I take the ~/.xinitrc and just 
rename it and put it in ~/.xinitrc.d, what's the difference? Why is that better?

The directory ~/.xinitrc.d doesn't exist by default. Is there any reason to 
expect that something else will need to go there?

My concern is that if I create a script in ~/.xinitrc.d that invokes window 
manager A, and then sometime in the future another script is placed there that 
is invoked window manager B, then we have a problem: two window managers will 
try to be invoked.

If I am trying to create an installer that automates the setup for a different 
window manager, there's no way for the installer to know which previous startup 
script has to be disabled in ~/.xinitrc.d. If ~/.xinitrc.d is used, changing 
window managers would require editing the files by hand. Using ~/.xinitrc seems 
like a better solution to prevent that condition and allow an automated 
install. Do you have a suggestion for how the installer can manage the 
automated window manager change in ~/.xinitrc.d without creating this potential 
condition?



_______________________________________________
Xquartz-dev mailing list
Xquartz-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev

Reply via email to