Installer removes "outdated" folders, doesn't install new ones!
Installer removes "outdated" folders, doesn't install new ones!
- Subject: Installer removes "outdated" folders, doesn't install new ones!
- From: Stephen Greenfield <email@hidden>
- Date: Fri, 07 Mar 2008 15:13:37 -0800
- Thread-topic: Installer removes "outdated" folders, doesn't install new ones!
Title: Installer removes "outdated" folders, doesn't install new ones!
I'm seeing a problem where the installer deletes outdated folders from a previous version install, but then fails to install the new folders of the same name.
For example: I have application folder "FooAppFolder", located in ./Applications.
Inside FooAppFolder are folders folder1, folder2 and folder3, plus the application package TheApp. TheApp is version "6.0.2". It was installed using a installer package created with Packagemaker 2.5.
NOW, I'm going to replace the components inside FooAppFolder, using a new package I've created using Packagmaker 3.0.1.
Mysteriously, folder1 and TheApp are updated, but folder2 and folder3 have been deleted, and the new versions that should have been installed missing.
If I delete the folder FooAppFolder BEFORE running the installer, then everything is installed into a fresh folder.
The Allow Relocation checkbox is off.
Does this failure to copy/update existing folders ring a bell with anyone?
Stephen Greenfield
Write Brothers, Inc.
_______________________________________________
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