As said on the "Installation Scripts" page in the introduction section, WarpIN requires installation scripts to receive additional information about the binary data in an archive. Scripts are stored in compressed form in the archive themselves and read when WarpIN attempts to open an archive on install.

Installation scripts basically contain two things:

  1. Information about the packages in the archive. This in turn falls into two categories: package information that is displayed to the user during install only and information that is stored in the global database on successful install.

  2. In addition, the scripts contain instructions for WarpIN about the pages in the WarpIN window that the user will go through during the install process (before files are actually unpacked).
WarpIN scripts are XML-compliant. If you don't know what XML is, don't worry... you don't have to buy a 500-page book and read it before you can use WarpIN. This documentation contains all you need to know.

Please see the "About XML" section in this book to learn more about XML in general and why we chose to make WarpIN XML-compliant.

See "Changes..." if you have used WarpIN's old script language before and want to know what has changed.

Otherwise see "Getting started" to learn how you can write your own installation scripts.