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: Martin Bestmann <email@hidden>
- Date: Tue, 13 Nov 2007 00:09:03 +0100
On 12.11.2007, at 23:31, Stéphane Sudre wrote:
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.
Hi Stéphane,
you were pointing me to the right direction. The problem is not in the
installer (because as you said the token search is really inside the
package) but the problem is in the packagemaker command line tool. We
are calling package maker from the command line with the following
(Tiger compatible) command line options:
-build
-p
-r
-b
-s
-i
-d
-r
We even provide the info.plist file. It seems to me that the
packagemaker adds the "IFPkgPathMappings" automatically by default.
Which I think is not the right thing to do. Does anyone know if there
is a way to tell packagemaker via command line on Leopard to not be
"smart" and NOT add the "IFPkgPathMappings" or is my only option to
manually remove the "IFPkgPathMappings" key from the "info.plist"
after the creation of the package?
Thanks,
Martin _______________________________________________
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