-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2008-12-08 at 12:26 -0500, Ken Schneider wrote:
Carlos E. R. pecked at the keyboard and wrote:
On Monday, 2008-12-08 at 08:15 -0500, Ken Schneider - Factory wrote:
In the filter view droplist there is one that shows everything that is going to be installed.
Showing _what_ will be installed is not the same as _why_ it will be installed which is what a change list would show. This I believe is more inline with what the OP was looking for.
The 'why' is simple enough: the user requested upgrade to newer version if available on any of the configured repositories with their configured priorities.
No. The user saw upgrades _were_ available (when checking) and wanted to know why the upgrades were available.
I also at times see that and would like to see what generated the need for an upgrade I.E. change list.
But then that is how I view the request.
Eummmm... no, I think you or I or both are confused. I think the OP user told YaST to upgrade all available. ] One question is, when I want to see all possible updates available. ] I notice that I can go to YaST -> Software management. ] Then click on Package -> All Packages (or "all in this list") seems to do ] that. It is not an automatic upgrade, it is a manually triggered upgrade of packages to a newer version if one is available on the selected repos (this I know), and it has a higher priority that the one currently installed (this I guess). When you start YOU and it says "Hey, you have updates!" then it is because there are mandatory patches or updates in the repository that is known to be the update repo (only one has that property, afaik). However, I don't know if it would be doable to click on one of the packages to be updated and see a help hint message and say why that particular package is going to be updated to that particular version. Perhaps show a list of available options and say why each one was discarded and another one chosen. Too many variables: dependencies, user choices... I think all that info is in the solvercase file, though. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkk9gA8ACgkQtTMYHG2NR9VcYACcDtY0KrrotrePuWpZf2GGLhig PREAn1JenhnHmhEkBpoWZo6iN4u8mAmb =dVES -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org