Re: minimal upgrade patch
Re: minimal upgrade patch
- Subject: Re: minimal upgrade patch
- From: "Clemmer, Everette" <email@hidden>
- Date: Tue, 22 Sep 2009 11:27:56 -0400
- Acceptlanguage: en-US
- Thread-topic: minimal upgrade patch
Title: Re: minimal upgrade patch
Thanks, that seems to do the trick!
Everette
On 9/21/09 4:23 PM, "Greg Neagle" <email@hidden> wrote:
Your upgrade package must have a different packageid and name than the original package.
Original package:
name/CFBundleName: MyGreatApp
packageid/CFBundleIdentifier: com.foo.mygreatapp.pkg
version/CFBundleShortVersionString: 1.0.0
Upgrade package:
name/CFBundleName: MyGreatApp _101
packageid/CFBundleIdentifier: com.foo.mygreatapp_101.pkg
version/CFBundleShortVersionString: 1.0.1
See Apple's iLife original packages and subsequent update packages for examples.
-Greg
On Sep 21, 2009, at 11:58 AM, Clemmer, Everette wrote:
Hi all,
I’m trying to do a minimal upgrade patch for my application. For some context, a minimal upgrade is an installation of only the files that have changed between two releases. I have a diffing script that will produce a package containing only the changed files, however, when I run the package, the old app is entirely replaced by the minimal app. I want to install the new files over the old app in such a way that the older files are replaced by the newer ones without destroying the whole install. I think what I’m trying to do is an upgrade installation, but I can’t seem to force that to happen. Any thoughts?
Thanks,
Everette
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden