|
Bugzilla – Full Text Bug Listing |
| Summary: | software manager: provide info about current package size in the list | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | macias - <bluedzins> |
| Component: | YaST2 | Assignee: | Stefan Hundhammer <shundhammer> |
| Status: | RESOLVED INVALID | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | yast SM | ||
Uh, I don't understand it, where do you see 130MB? I see 11.2MB... The simple task is simple in yast - select "Installation Summary" filter, uncheck all check boxes except "Protected", check "Keep". Click header "Size" in the table twice (to sort it from the biggest to the smallest package) and that's it. Now you can easilyy uninstall some large packages which you don't use... > Uh, I don't understand it, where do you see 130MB? I see 11.2MB... :-) See it for yourself. > The simple task is simple in yast - select "Installation Summary" filter, > uncheck all check boxes except "Protected", check "Keep". Click header "Size" > in the table twice (to sort it from the biggest to the smallest package) and > that's it. Now you can easilyy uninstall some large packages which you don't > use... That's exactly what I did, but it does not work that way -- compare sizes really carefully. When the newer package is available the size shown is the size of newer version, not the one installed. Created attachment 181433 [details]
yast SM
Oh, I see, it seems that the value in the table doesn't respect the selected filter. The displayed size in the table is always the candidate (if there is one). The size of the installed package is available in the "technical details" view. Besides, there is usually not very much difference in in size between different versions of the same package. The "k3b" example in that screen shot is a pathological exception. And trying to cut the discussion I can see on the horizon short: That package selector is already very complex. We sure don't want to add to the complexity even more unless absolutely necessary. |
It could be done by adding column (bad), settings in yast, or just a checkbox menu item in menu ("show current package size"). Now yast shows size of packages that MIGHT be installed -- and thus it makes maintaining the system more difficult it could be. Simple task -- show all biggest packages installed in the system. With yast it is impossible (for example the top entry is k3b with size ~130MB, but k3b is actually installed and it takes only ~11MB so I should now worry about it).