https://bugzilla.novell.com/show_bug.cgi?id=276494 ------- Comment #8 from sven.burmeister@gmx.net 2007-05-31 02:45 MST ------- Simple example: There is a patch to update package x from 1.0 to 1.1, nothing else, just one package. I use YaST to update some packages and that update is selected too. YaST performs the update, so patch or update, everything is done except the paper-work, i.e. acknowledge that the patch has really been updated. So for this step the user has to open the online update, select those patches manually and install them again. It absolutely does not make sense for the user to install them again, because installing something means to overwrite the existing package, even if that is not what is done, it is what is mediated to the user because that is what YOU normally does: If a patch is selected, it installs the version of tha package shown in the right pane. As a user why would I want to overwrite a newer package-version? I do not and hence the user does not know what to do with those "all dependencies met" (it is not even translated) patches. All this could be avoided by simply doing the job in YaST, if there is nothing else left than paper-work. This is a user's point of view which results from what the GUI and the applications mediate, so if it's wrong, they do not mediate their functionality correctly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.