Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct
Problem generating an Installer with Qt Installer Framework wich acts like an Hybrid Installer
fyDe last edited by fyDe
I am trying to create an installation routine using Qt Installer Framework.
From my point of view, there are 3 possibilities for the installation routine:
- Offline Only (will never be able to access servers to get updates)
- Online (Access to the repository and can be updated.)
- OnlineOnly (Access to the repository and can be updated. If the initial installation is used, the packages are loaded from the repository)
However, what I want to implement is an installer that works offline and additionally has access to the repositories. So the installer should install initial with the provided packages in the Installer and after that can also access the update repositories.
In the documentation
It can be seen that the hybrid function is still a TODO.
Can someone help me whether such an installer is currently implementable?
I look forward to your answers
Thank you very much
That's a question I'd recommend bringing on the interest mailing list. You'll find there Qt Installer Framework developers/maintainers. This forum is more user oriented.
hulahoopian last edited by
I wonder if you ever found an answer to this issue ?
I have a similar requirement, in that I want to create an online installer that works both ways. It needs to be able to be run in "download-only" mode (no installation, just download the repo). Then my client's IT dept can have a copy of the repo to put on their server, and their users (some of whom don't have internet access) can do a local installation from their local repo.
It seems that most of the functionality exists:
- The offline installer will create a local repo if asked to (CreateLocalRepository in config.xml). This could then be relocated to their server.
- The online installer can be forced to act like an offline installer by pointing it the local repo.
What I can't seem to do is combine 1 and 2 in the same installer. I could create both an offline and an online installer (one for client's IT and one for their users), except that I cannot package all components into the offline installer because some are licensed, and the client should only have access to the components that they have a licence for.