[master] Two ways how to fix the #1008788 blocker

Vratislav Podzimek vpodzime at redhat.com
Tue Sep 17 09:38:48 UTC 2013


My commit 5634449a1645343f3be340aa39faebdd5436ab35 causes that the TUI
ProgressHub is not scheduled/run because it provides no spokes and the result is
that the actual installation is skipped, because it is triggered by the hub.
There are two ways how to fix this issue:
1. always schedule the TUI ProgressHub
2. make ProgressHub a standalone spoke

I'm for 2. because the ProgressHub really is not a hub. It outputs a lot of text
to the standard output and thus it cannot provide any spokes as those would be
rolled off soon after the installation begins. However, 1. is much shorter and
probably less invasive.

-- 
1.7.11.7



More information about the anaconda-patches mailing list