site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com which had: Chris -pmb _______________________________________________ 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/ryanc%40apple.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... One other way to do this is to build a sparse package of 1.0.1 and have a file in the Resources folder named "Hints.plist" <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http:// www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <array> <array> <string>/*</string> <string>dontobsolete</string> </array> </array> </plist> This will instruct the installer not to remove items that existed in the old package and not the new package. At 11:17 AM -0800 3/1/06, Nathan Herring wrote: I can create a installer package for say the 1.0 version of my product suite. Beyond a few applications, there's a large number of supporting frameworks and files. Great. Now, I need to edit two of the largish applications for a 1.0.1 release. In the old days, we could use VISE and patch the two largish applications, probably using whatever binary diffing format they have. Is there any such process for the Apple Installer? Is there a way to patch rather than overwrite? Is creating the upgrade installer just a matter of having a sparse installation folder and archiving that, or are there other instructions? There isn't explicit support for this, but we're considering it for a future release. The workaround is pretty simple: just create a package that the installer won't realize is an 'upgrade' of your old package, and only put the modified files in the new package. That gives you a 'sparse' package, and the installer won't delete any of the missing files as long as it doesn't match your package to the older version by CFBundleID or package name. This email sent to ryanc@apple.com This email sent to site_archiver@lists.apple.com