Script

	Many software packages use scripts during installation and uninstallation to process files on the user's machine, display splash screens, or even launch installation notes. We recommend dividing each of the actions you need to perform into separate scripts. Package installers will then be able to provide feedback to the user as your scripts are executed.

	Are there any scripts to execute for this package [Y/N] ?
	(options: Yes,No)

Script Command Type

	A script may either be a private script, or a command referring to a previously-installed program. Private scripts are copied into your package and will not be visible to the user within their filesystem; they are stored in the repository only. Previously-installed programs may include software from another package or from the base installation.

	What type of script are you calling?
	(options: Private Script,Command)

Script Command

	Specify the location of the script file with respect to your current working directory. This file will be copied into the package and be marked for execution.

	What is the script command?

Script Command

	Enter the string you want to be executed, as if it were a command-line reference, with all application filenames fully qualified.

	What is the script command?

Major Script Event Timing

	The script can be set to execute at a number of different points during the life cycle of your package. You can choose the moment when your package is installed, activated (use), deactivated (unuse), or uninstalled.

Here are some examples of possible script timings:

Pre-install: This is called when the files have been initially placed in the user's repository.

Post-deactivate: This is a temporary uninstallation. At this point, the user has requested that the package be temporarily removed from their system.

Post-uninstall: At this point the package has been removed from the local repository.  You cannot refer to a script that is within the package. You can only run programs which are available on a base QNX Realtime Platform installation (ie: voyager -u http://www.qnx.com).

	Upon what event should this script be called?
	(options: Install,Use,Unuse,Uninstall)

Minor Script Event Timing

	Choose whether to execute the script just before the event (Pre) or just after the event has taken place (Post).

	When should this script be called [minor] ?
	(options: Pre,Post)

Script Blocking

	When the package installer runs your scripts, it has the option of waiting for your script to finish running before continuing with other installations. Frequently, scripts which interact with registration servers, launch web pages, or welcome documents should block.

	Should the package installer wait while this script is running [Y/N] ?
	(options: Yes,No)

Script Name

	Each script must be given a name which is used to describe what action will be performed. For example, Purge undeleted files, Install shortcut to desktop, or even Display readme.

	What is the name for this script?

Script Type

	Any scripts that you execute should not reference processor-specific executables or other processor-specific scripts. The answer to the following question should be NO, but if you choose to answer YES, your are implementing a feature not currently available in the package installer.

If this script runs binaries for a specific processor or executes shell scripts which have processor-dependent calls, this package must be marked as such. Making this distinction is important when installing packages onto file servers which are distributing files for foreign processors (ie: an x86 file server installing PPC packages).

	Does this script use binaries or processor-dependent scripts [Y/N] ?
	(options: Yes,No)

Script Priority

	Each script gets a priority level which determines if it will be called. Users may choose to turn off recommended or optional scripts but cannot stop required scripts from running. Recommended scripts will be selected by default by a package installer.

	What is the imortance of this script?
	(options: Optional,Recommended,Required)

	Are there more scripts to add to this package [Y/N] ?
	(options: Yes,No)

Installation Dependency

	This package may require or recommend the installation or uninstallation of an external package (one not currently being made by packager). This is especially useful for packages which require libraries, like Gtk, or supporting applications, like Python or Perl.

	Does this package depend on any external packages [Y/N] ?
	(options: Yes,No)

Dependency Type

	You may require or recommend the installation or uninstallation of another package. The QNX Package Installer will try to enforce your requirements before installing this software.

	What is the installation requirement?
	(options: Install,Uninstall,RecommendInstall,RecommendUninstall)

Dependency Notes

	You should provide a brief description of why you have added this requirement. Upon installation, the user will see this requirement note if they cannot meet your requirement. For example: This package requires the Gtk library for display in XPhoton.

	Please enter a requirement note.

Dependent File

	You add a package dependency by selecting a file which this software needs. If the file belongs to a package, a dependency will be added. For example, your application may require the Gtk package. The Gtk package provides the library glibc. By entering in /opt/lib/glibc.so.1, a dependency to the Gtk package will be added.

	What is the path to your dependent file?
	(determines the package from which the chosen file originated)

Product Home Repository

	If the user does not have the required package available in their repository, the QNX Package Installer may be able to find the package if you provide a home repository. The package repository should contain a current version of the package you require.

	What is the home repository of the dependent product?

	Are there more dependencies for this package [Y/N] ?
	(options: Yes,No)

Photon Launch Menu

	How many LAUNCH menu items?