Difference between revisions of "Documentation/Labs/AutomaticUpdateAndInstallationFramework"
From Slicer Wiki
| Line 1: | Line 1: | ||
Use cases: | Use cases: | ||
| − | * | + | * New Slicer version installed locally should be updated with the list of extension previously installed. |
| − | * | + | * Self update of Slicer |
| − | == Notes | + | = Keep track of the installed extensions across version = |
| + | |||
| + | == Current Process == | ||
| + | |||
| + | == Proposed Changed == | ||
| + | |||
| + | TODO | ||
| + | |||
| + | = Notes = | ||
| + | |||
| + | == 2016.05.03 == | ||
* See also [[Documentation/Labs/ExtensionsFrameworkRoadmap]] | * See also [[Documentation/Labs/ExtensionsFrameworkRoadmap]] | ||
Revision as of 15:53, 3 May 2016
Home < Documentation < Labs < AutomaticUpdateAndInstallationFrameworkUse cases:
- New Slicer version installed locally should be updated with the list of extension previously installed.
- Self update of Slicer
Contents
Keep track of the installed extensions across version
Current Process
Proposed Changed
TODO
Notes
2016.05.03
- Ability to ask the installer (or Slicer) to install other extensions
- Would it make sense to transition to http://doc.qt.io/qtinstallerframework/ ?
- Serialize what is installed in you current Slicer
- Update of installed extensions:
Related issues
- 2779: Mechanism to keep track of the installed extensions across version
Todo
- Extract list of extensions installed. Look at npm for the format.
- Extension manager:
- Update ExtensionManageModel API so that "list" can be processed
- Update entry "Install Extension from file" to "Install Extensions from file" and support "tar.gz", ".json"
