Well, I think it is a real issue, but I'm mostly wondering if there
has already been thought put into how things like this could be
handled. My mock up is certainly lacking. It does assume that the user
understands what a dependency means. It also doesn't take into account
what packages actually need to be installed. The user may in fact
already have all of the dependencies installed or many more might be
needed due to the entire chain of dependencies. As I mentioned above,
calculating the actual dependencies every time a package is viewed
seems like it might be an expensive operation. Though synaptic does
seem to do this pretty quickly. Perhaps it could be done only on
clicking the Additional Details arrow, allowing you to actually say
something like "The following additional packages will need to be
installed." Although I suppose there is also a question of whether the
arrow itself is discoverable.

The main issue I have with something along the lines of what
PackageKit is doing is that we are already popping up the PolicyKit
authorization window. Popping up an additional window will mean that
in most cases the user will have to go through two separate windows to
install a package.

Ideally I'd like to see is some way for the user to have some more
detailed information about what they are about to do to their systems
with out having to be an expert, yet still be un-intrusive. Maybe it's
a lot to ask, but I set the imprtance to wishlist for a reason. ;-)

-- 
No information about dependencies being pulled in
https://bugs.launchpad.net/bugs/432879
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to