Bug 157313 - Package Manager: Installation Summary
Summary: Package Manager: Installation Summary
Status: RESOLVED INVALID
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 7
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Stefan Hundhammer
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-10 21:06 UTC by Andreas Gruenbacher
Modified: 2006-03-17 13:37 UTC (History)
1 user (show)

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 Andreas Gruenbacher 2006-03-10 21:06:04 UTC 
The Installation Summary view in the package manager is not always up to date, and is not updated even after doing a manual dependency check. It always seems to be up to date when turning Autocheck on.

I think that when before switching to Installation Summary and Autocheck is not selected, a manual check should be performed. I'm not sure if the conflict resolution should be performed in this case as well; probably not.

Without up-to-date dependencies, the Installation Summary view can be pretty misleading.

The fact that while in the Installation Summary view, packages are still listed after their state has changed so that they would no longer show up in this view could be considered a feature. The view should always show additional packages that become selected though (e.g., after performing a manual check).
Comment 1 Stefan Hundhammer 2006-03-17 13:37:28 UTC 
No. Switching to a filter view may not change any object's state. This is contrary to the idea of views. And for sure you don't want to be confronted with dependency problems when you switch views. Switching views means you continue to work on your package selection. You don't want anybody, much less an automatism like a solver run, interfere with your actions. If you want a resolver run upon every mouse click, you can switch "auto check" on. This is why we have that check box.