Re: Leopard installer too smart and overwrite existing app
Re: Leopard installer too smart and overwrite existing app
- Subject: Re: Leopard installer too smart and overwrite existing app
- From: Stéphane Sudre <email@hidden>
- Date: Mon, 12 Nov 2007 23:31:52 +0100
On lundi, novembre 12, 2007, at 10:03 PM, Martin Bestmann wrote:
Hi,
I'm facing a very odd issue with the Leopard installer. Here is what I
have:
I have a folder called /myApps in the root of my disk. Inside that
folder is a bundled Cocoa app called myDemoApp. Now I want to install
a copy of that app with the name "myDemoApp Copy". To do this I
duplicate myDemoApp and create a new installer package using
PackageMaker (destination "/myApps").
When installing this package, it will NOT create a new app "myDemoApp
Copy" but rather update the existing app "myDemoApp" in "/myApps".
[...]
I've filed this as RADAR #5595385.
Well, it's not a bug, it's a feature!
In PackageMaker 3, by default, when you add an application, a relocator
will be automatically created for it.
Check the components panes of the package for your application bundle
in PackageMaker 3. You will need to uncheck the Allow Relocation option.
Be sure to have a different identifier for your package if you want to
have both applications at the same time.
_______________________________________________
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