Difference between revisions of "Documentation/Labs/AutomaticUpdateAndInstallationFramework"
From Slicer Wiki
| Line 1: | Line 1: | ||
| + | |||
| + | Use cases: | ||
| + | * new version installed locally should be updated with the list of extension previously installed | ||
| + | * self update of Slicer | ||
| + | |||
| + | == Notes from 2016.05.03 == | ||
* See also [[Documentation/Labs/ExtensionsFrameworkRoadmap]] | * See also [[Documentation/Labs/ExtensionsFrameworkRoadmap]] | ||
Revision as of 15:33, 3 May 2016
Home < Documentation < Labs < AutomaticUpdateAndInstallationFrameworkUse cases:
- new version installed locally should be updated with the list of extension previously installed
- self update of Slicer
Notes from 2016.05.03
- Automatic update of Slicer
- Ability to ask the installer (or Slicer) to install other extensions
- Would it make sense to transition to http://doc.qt.io/qtinstallerframework/ ?
- Mechanism to keep track of the installed extensions across version. See http://www.na-mic.org/Bug/view.php?id=2779
- Serialize what is installed in you current Slicer
- Update of installed extensions:
