[Xquartz-dev] 2.3.0-rc1

[Chupacerveza]

10.5.3 can be found where? I'm an ADC member, but not seeing it, so I'm 
curious.

Thanks,
Robert

Jeremy Huddleston wrote:
> To be honest, I've been pretty much sitting on this since about 
> Thursday.  I wanted to wait until 10.5.3 was out to avoid possible 
> clobber issues that I saw resulting from the new startup code... but 
> someone who has access to the developer seeds needed some of these fixes 
> in pkg form, so I figured I'd push it out.  For the rest of you, you'll 
> get most of these updates just by installing 2.2.1 and dropping in the 
> http://xquartz.macosforge.org/downloads/Xquartz-1.4.0-apple8.bz2 
> update.  I think the only thing I've changed since then has been the 
> startup path, so you're not really missing much.
> 
> --Jeremy
> 
> 
> On May 13, 2008, at 08:22, Jamie Kennea wrote:
> 
>> Hi,
>>
>> How about a version for those of us that are smart enough to reinstall 
>> when 10.5.3 comes out? Or is there a work around so I can install it 
>> on 10.5.2?
>>
>> Or do I not have too long to wait for 10.5.3. ;)
>>
>> Jamie
>>
>> On May 12, 2008, at 7:55 PM, Jeremy Huddleston wrote:
>>
>>> I've just finished uploading the first release candidate for the next 
>>> X11 package installer.  You can find it here:
>>>
>>> http://xquartz.macosforge.org/downloads/X11-2.3.0_rc1.pkg
>>>
>>> Some notes (IMPORTANT, READ ME!!!):
>>> The installer requires 10.5.3, so if you don't have access to a seed 
>>> of 10.5.3, you'll have to wait until release.  This package doesn't 
>>> "really" need 10.5.3, but I don't want people to install the 10.5.3 
>>> OS update after this package and then forget to reinstall X11 because 
>>> it will cause some issues due to the new startup mechanism (you'll 
>>> loose the X11 menus, etc).
>>>
>>> As of 2.3.0-rc1, the server bits are actually located in the bundle. 
>>> /usr/X11/bin/Xquartz is just a stub that "does the right thing" to 
>>> start the server (for now, it's just doing an exec(), but it will be 
>>> done via Mach-IPC in the future).  This allowed us to clean out all 
>>> the extra cruft we had in xinit.  There are some side-effects to note:
>>>
>>> If you copied or moved your X11.app bundle from its default location, 
>>> you will need to update the copy with the new one after 
>>> installation.  If you don't, you run the risk that 
>>> /usr/X11/bin/Xquartz will find the old one and you'll see messages to 
>>> Console.app indicating this.  If X11 fails to start after updating to 
>>> 2.3.0, this is the most likely culprit.  Check Console.app for 
>>> debugging messages that will tell you the location of X11.app that 
>>> Xquartz is finding.
>>>
>>> You will not be able to use any of the Xquartz binaries from previous 
>>> releases with this release, and visa-versa.  That is why I haven't 
>>> made an updated binary drop for a while.  From now on, you'll need to 
>>> grab X11-1.4.0-appleXX.bz2 and drop it over 
>>> /Applications/Utilities/X11.app/Contents/MacOS/X11 rather than 
>>> updating /usr/X11/bin/Xquartz.
>>>
>>> ChangeLog:
>>> http://xquartz.macosforge.org/trac/wiki/ChangeLog
>>>
>>> _______________________________________________
>>> Xquartz-dev mailing list
>>> Xquartz-dev at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo/xquartz-dev
>>
>> _______________________________________________
>> Xquartz-dev mailing list
>> Xquartz-dev at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo/xquartz-dev
> 
> _______________________________________________
> Xquartz-dev mailing list
> Xquartz-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo/xquartz-dev