http://bugzilla.suse.com/show_bug.cgi?id=1135366
http://bugzilla.suse.com/show_bug.cgi?id=1135366#c1
Martin Vidner changed:
What |Removed |Added
----------------------------------------------------------------------------
URL| |https://trello.com/c/Xpjm7K
| |dr
CC| |mvidner@suse.com
Assignee|yast2-maintainers@suse.de |yast-internal@suse.de
--- Comment #1 from Martin Vidner ---
I see two distinct parts:
1. showing a progress report while YaST is busy
2. if an error occurs, giving the user the possibility to stay in the module
and retry or correct things
(1) is standard behavior, we should simply do it
(2) is unusual in YaST, only the package manager does it IIRC. It is also
problematic in that we would go a different way than the usual
1. initialize everything
2. perform changes (mutate internal state)
3. quit, discarding the state
to
1. init
2. mutate
3. report a problem
4. further mutate the problematic state, what could possibly go wrong?
Or have I misunderstood and the point is simply to report errors?
--
You are receiving this mail because:
You are on the CC list for the bug.
