James J Catchpole wrote:
I am not sure if anyone has commented on the Add/Remove Software function but I find it almost impossible to use. Following are a couple of comments:
- It appears that you can only Add or Remove one package at a time.
I have filed this one. Still on discussion about what the user interface should look like. Note that the PackageKit allows you to queue transactions. So you can install multiple packages without the UI blocking.
I am unable to figure out how to queue up updates. that should be the default in any case.
From an End User Perspective there should be a section on the panel that prints out the status of updates as they occur. More or less as Yum Displays the output as each package is installed.
There should be a section on the panel that lists the queue of packages being removed, updated or installed.
- The Filter function is almost useless
A better explanation is needed here.
Well, its not granular enough; I should be able to choose what I want to see at the package level, not the category, perhaps with radial buttons.
I also should be able to pick multiple categories rather than one at a time; again perhaps with radial buttons. Radial Button Examples for Categories might be:
o List this Category o Do not list this category
o Installed Packages o Available Packages o All Packages
And then at the Package Level the same three radial buttons that would override the category choice. Also there should be additional radial buttons indicating whether or not a given package should be:
o Ignore Package [Default] o Update Package o Install Package o Remove Package
- After every Install | Remove the entire list must be refreshedRe: fedora-test-list Digest, Vol 50, Issue 128
Within the group. Otherwise you wouldn't be able to see a confirmation that the package has just been installed successfully. The refresh is sometimes not visually appealing especially when listing a large number of packages within a group which is reported already.
I see no reason why this is necessary. The combination of the YUM Return Codes and a section of the panel that lists events should be enough. Also, there could be additional Status Buttons along side each Package in the list of queued packages indicating what happens as the packages are processed. The same would be true for prerequisite packages that should be listed in the queue of packages to be processed as they are processed.
- Depending on 'whatever' it often displays Packages multiple times
Already filed by me.
Rahul
James J Catchpole wrote:
James J Catchpole wrote:
I am not sure if anyone has commented on the Add/Remove Software function but I find it almost impossible to use. Following are a couple of comments:
- It appears that you can only Add or Remove one package at a time.
I have filed this one. Still on discussion about what the user interface should look like. Note that the PackageKit allows you to queue transactions. So you can install multiple packages without the UI blocking.
I am unable to figure out how to queue up updates. that should be the default in any case.
If you're talking about installs rather than updates, Click install, select another item, click install. It works for me with the latest version of PK in rawhide. Any other operation that PK performs (update, refresh software list, etc) should queue in the same way.
From an End User Perspective there should be a section on the panel that prints out the status of updates as they occur. More or less as Yum Displays the output as each package is installed.
There should be a section on the panel that lists the queue of packages being removed, updated or installed.
There is such a list, it is part of the gpk-update-icon tray icon for the gnome panel (I don't know if it works in KDE?). When clicking on the icon it shows the current queue of operations, clicking on any one item in the queue shows the status window for that operation.
James J Catchpole wrote:
James J Catchpole wrote:
I am not sure if anyone has commented on the Add/Remove Software function but I find it almost impossible to use. Following are a couple
[snip]
As far as I'm concerned, yumex does everything I need. Why all the complicated (and broken) package managers that are nothing more than difficult to use yum wrappers?
The new packagekit stuff looks interesting, but it's obviously broken, difficult to configure, and even more difficult to turn off.
Rainman
James J Catchpole wrote:
I am unable to figure out how to queue up updates. that should be the default in any case.
[Please stop using html mail. A yellow background is just obnoxious]
It is the default. Clicking on a package to install it queues it without blocking the UI and you can click on the next package to queue it.
Well, its not granular enough; I should be able to choose what I want to see at the package level, not the category, perhaps with radial buttons.
File a bug report.
I see no reason why this is necessary. The combination of the YUM Return Codes and a section of the panel that lists events should be enough.
You have to figure out how to display it within the user interface regardless of the implementation details. Again, if you got better ideas, file bug reports.
Rahul
Rahul Sundaram wrote:
It is the default. Clicking on a package to install it queues it without blocking the UI and you can click on the next package to queue it.
Huh? Clicking on a package selects it. Clicking on a second package un-selects the first package.
Furthermore, the standard shift-click and ctrl-click do not work as I would expect. (Shift-click is the same as plain click, and ctrl-click has no effect.) That seems like a bug to me.
Per Bothner wrote:
Rahul Sundaram wrote:
It is the default. Clicking on a package to install it queues it without blocking the UI and you can click on the next package to queue it.
Huh? Clicking on a package selects it. Clicking on a second package un-selects the first package.
Double click or click install.
Furthermore, the standard shift-click and ctrl-click do not work as I would expect. (Shift-click is the same as plain click, and ctrl-click has no effect.) That seems like a bug to me.
Rahul