PackageMaker don't overwrite requirement
PackageMaker don't overwrite requirement
- Subject: PackageMaker don't overwrite requirement
- From: Jack James <email@hidden>
- Date: Tue, 9 Feb 2010 11:21:05 +0000
Hi there
I'm trying to create an installer with packagemaker. So far it is all working. I have two packages- an application and the supporting data files.
What I want to do is this: only install the support package files if they don't already exist in the destination folder (i.e. prevent the installer from overwriting them). The packages are relocatable, and the user's home can be selected as a destination in addition to the disks.
It was sort of working if i used the "file exists on target" requirement, but it would invariably fail if I was trying to install to a home folder. So instead I opted to use a current choice: packageUpgradeOption!=clean which also sort of worked until I realised that the package would be set to upgrade even if the files had been deleted from the system.
I suspect I can use the fileExistsAtPath(filePath) _javascript_ function, but I'm not really sure what I'm doing with _javascript_; also it seems that filepath has to be hardcoded? - so it won't work when installing to the user's home folder.
I'm sure there must be an easy way to just select/deselect the package based on where the installer thinks it's going to put the files, but I'm too new at this… I did read somewhere about installing files to /tmp and then moving the files from there, but I have the same problem in terms of trying to figure out where the installer intends to put the files.
Thanks for any help
Jack
--
Sign up for the Synaesthesia beta:
http://synaesthesia.surrealroad.com/beta
www.surrealroad.com
_______________________________________________
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