Thanks for your response, Actually I am deploying a product which other than having the application bundle, has lot of other resources like Plugins bundles, libs, documents and what not. And all these other resources are not part of application bundle but need to be placed in the product's parent application folder along with the application bundle. I have created an installer for this product and have provided to our customers. Our customers generally have multiple drag copies of the install on their system. I didn't set the reallocation flag for any of the sub components including application, simply because
1. It allows reallocation flag to be set only for bundles, but not for other resources and folders
2. as in case there are more than one copies of reallocatable
files on the drive, the installer.app patches the first file found on the drive, without user know which installation copy has actually got patched?
Now I am planning for an update of my application with some customer reported defects. I don't want to spend time creating an updater for my application, rather want to use the same installer, So that for my new customers I can give them this installer having some critical defects already fixed, and for my existing customers, the same installer can be used to patch their existing installation.
So for this installer
1. I want to know if this is a fresh install or I need to patch my previous installation. (Probably this can be achieved my reading receipts)
2. In case I have to patch my previous install, then I want a way to know if more than one copy of my product is already present on his system, and to provide my customer option to choose the copy he wants me to patch. (This I
was planning to achieve by writing an installer Plugin)
2a. Then I wanted to set this user selected path to the custom location. Which is not possible????
Can you suggest any other alternative approach to achieve the above scenario?
-N
----- Original Message ----
From: Scott Amory <email@hidden>
To: Nethan Aryan <email@hidden>
Cc: email@hidden
Sent: Tuesday, July 1, 2008 10:17:44 PM
Subject: Re: Changing the custom install location
On Jun 30, 2008, at 11:16 PM, Nethan Aryan wrote:
Hi All,
I am writing an installer using packageMaker 3.01 and wanted to target Tiger and Leopard OS for my product. I have checked the "Allow alternate volume" check box for parent package, which means during installation at "Installation Type" dialog the user can choose some custom install location for that package.
Though I have specified the default location for the package at design time, but I don't always want to show the same default location, rather based on some conditions would like to show some other default location. So my question is can we change this custom location at
runtime?
Thanks
Nethan
Unfortunately, the custom location cannot be changed in this way during runtime.
Scott
