Qt SDK's installer framework settings
This article explains how to use the new advanced settings made available by Qt SDK's installer framework
The Qt SDK 1.2 release has a new Settings feature in the installer framework, which allows more more flexibility in specifying the network proxy settings as well as making more content visible to the SDK installer, from compatible repositories created and hosted outside of SDK's own repository.
The feature is available for both the online installer and the SDK maintenance tool and can be accessed through the new Settings button.
In the Network tab you can specify whether the installer needs to be aware of proxy settings specific to the network in which it is being used, in which case it can either be set to use your PC's current system proxy settings or your own custom parameters (including proxy authentication).
The SDK installer (and the maintenance tool) are build with an hard coded online repository URL which will be accessed each time the user request an operation (install, update, package management) which could require listing the available components or downloading the components themselves.
The new build of the installer framework allows for such repositories to be created and hosted separate from SDK's main repository. Once such content available, it can be added to the SDK's online installer (or later to the maintenance tool) as an user defined repository.
In the Repositories' tab in the Settings dialog the new repository is added by specifying its URL and, if required, the username and password which would grant access to repositories which have restricted access.
Once the new repository added, the dialog is closed and the operation of the installer/maintenance tool continues as in the previous releases, with one additional step: online repository scanning.
Once the repository accessed successfully, its content list is fetched and added to SDK's list of components, from where the respective items can be either added or removed from the list of the components to be processed in the next step of tool's flow.
It is repository provider's responsibility to document the behavior of the components and to ensure that the correct dependencies are defined and obeyed between the new added components and SDK's original content. It is also repository publisher's responsibility to make the new repositories known to the intended SDK users.
There is no security mechanism built-in so uses should only add URLs known to point to repositories they trust.