Re: how to avoid overwriting files during installation
site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On jeudi, décembre 22, 2005, at 08:55 PM, Patrick Litterst wrote: A quick look at the archive show a post from C. Ryan which may help: I assume you could have a hint that says: <array> <string>/*</string> <string>dontobsolete</string> </array> _______________________________________________ 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... I've created a .mpkg installer using PackageMaker that contains two packages: one package contains an application that gets installed in the Applications folder, and the other package contains files that get installed elsewhere on the computer. If the user reinstalls the application using the .mpkg installer, the files (which the user may have modified prior to reinstallation) will be overridden. How can I prevent these files from getting overridden during reinstallation of the software? [...] Yes, although I could find no public documentation. Do a search for "Hints.plist" in your receipt directory (find . -name "Hints.plist" -print). You will see a number of Apple packages which use the hints mechanism to prevent obsoletion in some cases. Basically saying don't obsolete anything (although you will have to try that out and see if it works). The problem is, that in the future when you do want upgrade behavior (to remove old files) it will see your "update package" which only contains a few files and you will have a hard time removing all the pieces of the original install on upgrade (if they are truely not part of your product anymore) without writing a script to do it by hand, since the last receipt for a given package is all that sticks around. [...] This email sent to site_archiver@lists.apple.com
participants (1)
-
Stéphane Sudre