Allow unstable components when categories are used

Unstable component means that the component has unresolved dependency,
script error etc. Installer cannot recover if we are already in
component selection view and fetch new packages from a category which
has unstable components if AllowUnstableComponent is false. Fixed so
that allowing unstable components is forced when categories are used.
Ideal solution would be to recover and rollback the install tree if
unstable components are found but that requires huge changes to IFW.

Task-id: QTIFW-1257
Change-Id: I786df1b8b54c238f50e15b94a06005e244417c97
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
Reviewed-by: Jani Heikkinen <jani.heikkinen@qt.io>
This commit is contained in:
Katja Marttila 2019-01-14 10:16:23 +02:00
parent cd5168de39
commit 7c3c796cbf
2 changed files with 6 additions and 1 deletions

View File

@ -1139,7 +1139,11 @@
By default, only repositories with no category are shown in the component selection widget. Checking one or
several repositories and pressing \uicontrol Fetch will update the widget to show content also
from the selected categorized repositories.
from the selected categorized repositories. Components in the repository
categories are marked as \e unstable meaning that you can install other
components although some components have missing dependencies, script
errors and so on. For more information about \e unstable components, see
\l {Summary of Configuration File Elements}.
Example of creating a repository category:

View File

@ -1913,6 +1913,7 @@ void ComponentSelectionPage::entering()
if (core->settings().repositoryCategories().count() > 0 && !core->isOfflineOnly()
&& !core->isUpdater()) {
d->showCategoryLayout(true);
core->settings().setAllowUnstableComponents(true);
} else {
d->showCategoryLayout(false);
}