- 
    Epic 
- 
    Resolution: Done
- 
     Not Evaluated Not Evaluated
- 
    None
- 
        Qt 6: Installer CLI and UI
Requirements for Command Line Interface tool & Installer UI
- Possibility to create standalone/static executable, all runtime dependencies need to be bundled
- Qt Account login integration
- Permission control per package
	- Per Qt package
- Per Qt package version
- Per product definition
- Per host & target platform (i.e. build configuration)
- Per other rules
 
- Commands:
	- List & inspect available packages, should provide information (meta):
		- Package name, title, description, build date, etc.
- Package version
- Package build configuration
			- host_os, host_os_version, host_arch, host_compiler
- target_os, target_os_version, target_arch, target_compiler
- other features (NoUseGoldLinker, Static, Release, NoWidgets, ...)
 
- Dependencies
 
- Install selected packages
- List installed packages
- Update selected packages
- Remove selected packages
 
- List & inspect available packages, should provide information (meta):
		
- Multi-platform (running the CLI/Installer)
	- Linux x86_64
- Windows x86/x86_64
- macOSĀ x86_64
 
- Possibility to control where selected packages are installed
	- White space in install tree is not allowed
- Define default install location
 
- Control scripting/component scripting per package
	- Write/read settings files
- Run system commands
- Create desktop shortcuts
- Access to information about other packages
- Catch events onInstallationStarted, onInstallationEnded
 
- Proxy handling
- Add custom package repositories, eg. market place or self built packages
- Customizable UI
- Headless installation/update
- Possibility to run program after installation (eg. launch QtCreator)
- Sending custom messages to server
- Hide certain packages in UI (current Virtual component)
- Force install of components
It should be possible to customize the UI, how the packages are shown to user:
- some licenses/products may have priority over others -> prioritize the visibility
- other possible "schemes"
- depends on
- 
                    QTIFW-1555 Provide developers with a CLI for the installer -           
- Closed
 
-         
- 
                    QTIFW-1335 Qt Installer UI improvements -         
- Closed
 
-