Leopard installer too smart and overwrite existing app
Leopard installer too smart and overwrite existing app
- Subject: Leopard installer too smart and overwrite existing app
- From: Martin Bestmann <email@hidden>
- Date: Mon, 12 Nov 2007 22:03:56 +0100
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".
Here is the essential part of the installer log
Nov 12 21:45:15 martin Installer[1593]: Processing my DemoApp:
Nov 12 21:45:15 martin Installer[1593]: Determining files to install
Nov 12 21:45:15 martin Installer[1593]: ./myDemoApp copy.app
installed to /myApps/myDemoApp.app
To make this even worse. If you do not have "DemoApp" in /myApps but
somewhere else (e.g. in /tmp) the installer will update that version.
Is this an intended behaviour?
Here are the exact steps to reproduce this:
- Create folder /myApps
- Copy any bundle app (e.g. create new sample cocoa app in XCode)
into /myApps
- Duplicate the app
- Create a package with PackageMaker with the duplicated app (the one
having the "Copy" at the end)
- Delete the duplicated app from /myApps and empty trash
- Install the created package
-> You will not get a second app in /myApps with "Copy" at the end of
the name but the existing app is overwritten
-> Check the installer log for additional info.
I've filed this as RADAR #5595385.
Best regards,
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