Re: package maker
Re: package maker
- Subject: Re: package maker
- From: Jim Dodd <email@hidden>
- Date: Wed, 24 Mar 2010 05:24:45 -0700 (PDT)
Title: RE: package maker
The script must be named InstallationCheck - using that exact name with the 'I' and the 'C' capitalized. No extension is allowed on the script. As was mentioned before, also make sure it is made Executable. You should have the script do a simple print to a text file so you know it ran without needing to worry about how the Installer reacts to it. Something as simple as:
#!/bin/bash
echo "InstallationCheck is running" > ~/InstallLog.txt
will create a text file in your home folder and should be enough to start. Are you sure you are using a scripting language that is supported?
Regards,
Jim Dodd
Onset Computer Corporation
From: spondita Madhuri Neog <email@hidden>
To: email@hidden
Sent: Wed, March 24, 2010 3:16:06 AM
Subject: RE: package maker
Hi,
I have tried putting the InstallationScript and InstallationCheck.strings file in my scripts folder along with the pre and post-install scripts In my InstallationScript, I have made a check whether my application is running and display a corrresponding error message in InstallationCheck.strings file.But the package does not seem to have taken these into account and proceeds with the installation process as usual even if InstallationScript fails. The installation is not aborted and no error message is displayed.
_______________________________________________
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