On 25 Oct 2009, at 6:28 PM, Paul Messmer wrote:
I'm trying to build simple application installers (one for 10.4, one
for 10.5+) that place required files into Application Support as
well as the application itself into the Applications folder. Our
current installers (built with a superset of the script below) work
fine on a clean machine. The problem is that if a version of the
app already exists somewhere else on disk when installer is run, the
installer overwrites that copy of the app instead of installing into
the Applications folder - what we'd like. This could create a
number of tech-support issues that we'd rather avoid. Is there a
reasonable way to get the installer behaviour we want (always simply
have it install a fresh copy of our app into /Applications?) The
version of PackageMaker is 3.0.2 (174).
Installer.app has a feature that tracks down a copy of a previously-
installed application and updates it, in case the user moved it to a
more convenient place. This is called "relocation," and there is a
flag you can set in PackageMaker to turn it off.
However, PackageMaker sets it randomly even if you turn it off. This
is a bug of years' standing. You can expect a number of years-old bugs
in PackageMaker.
You deal with this by editing the raw project file before each build,
preferably with a script you can put into a makefile.
Details in the archive of installer-dev, to which you should direct
your followups.
— F
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
