Re: Installation destination path from a script
Re: Installation destination path from a script
- Subject: Re: Installation destination path from a script
- From: Christopher Ryan <email@hidden>
- Date: Tue, 9 May 2006 20:14:23 -0700
Since many paths inside your package can relocated, there is no simple
way to pass this list to these scripts.
We are aware of this restriction and hope to provide a better solution
in the future.
Chris
My simple question is: is there a way from a postflight script to
know where the installer has located the existing software it will
update?
My package uses a LaunchServicesLookup rule to locate our existing
game application. That works great. But I'd like to know this
location from within a script. I've not found any script variable
that gives me this info. $2 is supposedly the path to the
installation destination, but that always returns "/". None of the
other variables (such as INSTALLER_TEMP, PACKAGE_PATH, RECEIPT_PATH,
and TMPDIR) get me close either.
What I'm trying to do:
I need to delete and/or move files associated with the game I am
updating. Our installation consists of an enclosing folder that
contains the game app & several data files. Some of these data files
need to be deleted and/or moved. The game was originally installed
via drag-install.
_______________________________________________
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
_______________________________________________
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