Re: OS update
Re: OS update
- Subject: Re: OS update
- From: Jeremy Huddleston <email@hidden>
- Date: Wed, 07 Dec 2011 12:48:06 -0800
On Dec 7, 2011, at 8:02 AM, Martin Costabel wrote:
> Hans Kruse wrote:
>
>> On Dec 7, 2011, at 5:18, Pierre Baguis <email@hidden <mailto:email@hidden>> wrote:
>>> Thank you guys for the great info. There are some points though that need clarification.
>>>
>>> (1) I am a little bit confused about the fate of an existing X11 installation. What I have in the Macbook is the initial (from the DVD) X11 installation on top of which the XQuartz updates were applied. So, if I just update the system (Leopard --> Snow Leopard) without erasing the hard disk and wishing to use the existing Fink installation, should I just apply the latest XQuartz version for SL?
>> The SL install will overwrite the XQuartz install from Leopard, so you end up with a stock X11. Whether you want to install XQuartz after that depends on what you need from X11. Fink and MacPorts have recommendations on the best X11 environments for their systems. On SL the stock X11 and XQuartz exist side by side, but there are still cases where package managers can get confused.
>
> There is one case where the outlook is not so rosy:
>
> If your version of XQuartz on Leopard was higher than 2.3.6 and you built packages that used this, then you are in trouble: Your binaries will link to library versions in /usr/X11 that don't exist any more on SL. The "new" X11 in /usr/X11 has lower version numbers for a couple of libraries, and XQuartz for SL installs its libraries someplace else. Therefore your binaries will crash, and you will need to rebuild them with the new X11. For Fink this means that you will need to rebuild almost all packages.
One way around this is to simply install XQuartz and:
sudo mv /usr/X11 /usr/X11.bak
sudo ln -s /opt/X11 /usr/X11
> This is a known design flaw in the XQuartz project.
Or another way to say it is that there is a design flaw in the fink project, seeing as how I told them how to do it correctly (build against the SDK or package your own X11 libs) years ago, but the point is moot now. FWIW, MacPorts does the right thing and won't have issues like that.
> I have always warned people not to install any XQuartz version after 2.3.2 on Leopard if they thought of upgrading to SL later on.
What's wrong with 2.3.3?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden