Renaming application and the relocatable flag on upgrade
Renaming application and the relocatable flag on upgrade
- Subject: Renaming application and the relocatable flag on upgrade
- From: Jaroslav Šnajdr <email@hidden>
- Date: Tue, 06 Mar 2012 17:25:47 +0100
Hello everyone,
we have an application that, in current version, is named OldApplication.app and is installed under this name to /Applications by our PackageMaker package.
Now we'd like to rename the app to "NewApplication.app" in the new version. However, the upgrade turns out to be a little problematic.
a) If the package allows relocation, then the installer finds an already installed version in /Applications/OldApplication.app. It decides to relocate the installation to that directory. That means that the app remains installed with the old bundle name.
b) If I turn off the relocation, then the app is installed correctly into /Applications/NewApplication.app. However, the old version remains installed as /Applications/OldApplication.app. The only solution I see is to delete the old version by the postflight script. And of course, if the previous version was installed in a custom location, the installer won't find it. The benefits of relocation are lost.
What I would like to see is the best of both options: leave the relocation on, but please rename the bundle to the new name. Is that possible?
Jarda
_______________________________________________
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