Bug in Package Maker causes Mayhem
site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... Since upgrading to XCode 3.1 and presumably Package Maker 3.0.2 it seems that the Destination is no longer persisted. I only found out about this problem the hard way after testing my package installation and installing everything in the root of my drive. Initially I thought that this would be not too big a problem, however as it turns out during the installation some system files were overwritten, and I ended up with a broken OS. I spend 2 hours recovering form Time Machine, and still have to do the same on another system where I also "tested" the install package. Unfortunately the last time a I backup the other system was a couple of weeks ago, and now I have to spend a lot of manual effort on this. Well enough about me complaining, however I still would like to know why this happened. I almost shipped this to one of my clients and this would have broken his system as well. Maybe Package Maker is not the ideal method of distributing an Application. Maybe with all this iPhone hype, somebody got stuck in the cloud instead of testing. If anybody has any suggestions for a better solution to package and deploy application please let me know. This email sent to site_archiver@lists.apple.com
participants (1)
-
Alexander Hartner