Bug 117754 - YaST Update: Enhancing Software selection
Summary: YaST Update: Enhancing Software selection
Status: RESOLVED DUPLICATE of bug 104579
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: RC 4
Hardware: Other All
: P5 - None : Enhancement
Target Milestone: ---
Assignee: Jiri Srain
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-19 12:09 UTC by Karl Eichwalder
Modified: 2005-09-27 07:15 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Karl Eichwalder 2005-09-19 12:09:07 UTC 
My old system was "Minimal Textmode System" 10.0 which I intended to update to
"GNOME system".

When I selected "GNOME" YaST asked me:

"Do you really want\n"
"to reset your detailed selection?"

Since I did no do any "detailed selection" before, I think this question is not
appropriate in case the user updates the system.
Comment 1 Michael Gross 2005-09-19 13:25:00 UTC 
That's a matter of opionion I think. When you select one of these selections, it
might cause packages to be removed, which are not included in this selection. So
the message has its purpose. I'm not sure about this, so maby Jiří can give us
some clue here?

If packages are removed due to such an action, how should YaST really determine
if there was a detailed selection without checking the complete package-database
against the installed packages? Would be very time-consuming...
Comment 2 Karl Eichwalder 2005-09-19 14:03:26 UTC 
To make it clear, I went from "minimal" to "GNOME".  In this case, simply ask
the user whether he wants "to _change_ the previous software selection", but
better don't ask any question under those circumstances.  Only ask, if
deinstallation of packages of a customized system is involved.
Comment 3 Jiri Srain 2005-09-27 07:15:06 UTC 
Fixed yesterday. 

*** This bug has been marked as a duplicate of 104579 ***