Re: Xcode 2.0 upgrade glitch
Re: Xcode 2.0 upgrade glitch
- Subject: Re: Xcode 2.0 upgrade glitch
- From: email@hidden (Jack Howarth)
- Date: Fri, 6 May 2005 15:19:36 -0400 (EDT)
Markian,
The MacOS X 10.4 installer and the Xcode 2.0 installer are completely
separate. Indeed, if you have a MacOS X 10.3 volume with Xcode 1.5 installed
the old incompatible version of Xcode will remain after the MacOS X 10.4
installer is used to upgrade the volume. Normally this would just be an
annoyance. However since files (representing binutils I believe) have been
moved from the Xcode installer to the MacOS X 10.4 installer problems arise
over file ownership. The upgrade to MacOS X 10.4 installs files that 10.3
never owned and when the Xcode 1.5 present on the volume is then upgraded
these files are blindly removed since the uninstall script assumes they
belong to Xcode 1.5. Since Xcode 2.0 no longer installs these files, they
are effectively deleted from the drive.
Note that this problem won't occur if you do a clean install of
MacOS X 10.4 and migrate only the user accounts, applications and network
settings (but not the data and files). In this case when you install
Xcode 2.0 it will be treated as a new install rather than an upgrade and
old Xcode files (now belonging to BSD.pkg) will not be deleted. Likewise
you won't see this issue with a Archive and Restore install of Tiger.
In a perfect world, Apple would have file tracking in their installer
on the same level as rpm or dpkg so that such file ownership conflicts
would be caught at install time. Of course such a change would have its
own problems as users would like force install conflicting packages anyway.
Jack
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden