 | |
 | |
 | ||||||
contents
| 6.9 - Installation options Starkits and Tclkit are designed to be installation-free - one only has to copy or downloads individual files and they immediately become usable. One important consequence is that Starkits can make a minimal impact on the target machine: there are no registry settings (unless the application introduces them), there are no files strewn all over the disk, and there is no need to have super-user privileges to start using a Starkit. Deployment using Starkits can be summarised as:
The main benefits of this approach are:
But in some situations, the more familiar approach of a traditional “installer” may be appropriate (even if it does nothing more than copy a Starkit/Starpack to a local filesystem). There are a number of approaches to this:
The self-contained nature and smaller size of the last approach is definitely advantageous (especially when using network based distributions). To implement this, the Starkit can look for a copy of itself in a known location and, if not found, start the installation process. Alternatively, if using a Starkit you can use the ability of a Starkit to update itself and store a file inside the Starkit to indicate that it has been installed. This way the Starkit can check to see if it has been installed and, if not, start the install dialog. | see also | ||||
| | | | | | |