Mailinglist Archive: yast-devel (191 mails)

< Previous Next >
Re: [yast-devel] Package-Bindings
  • From: Stefan Hundhammer <sh@xxxxxxx>
  • Date: Thu, 20 Mar 2008 14:42:45 +0100
  • Message-id: <>
On Thursday 20 March 2008 14:05, Klaus Kaempf wrote:
3.) Select "Upgrade all (if possible, of course)"

Now what's "if possible, of course" supposed to mean ?

The point is, that the sat-solver provides just this functionality,
'compute all possible updates'. The result is 'solved', you won't get
any dependency conflicts.

This should be the default mode.

This discussion is becoming more and more abstract. It might help to simply
try using it rather than speculating about what it might or might not do.

The UI functionality this is (now) all about is not the regular system update.
It never meant to be anything like that. It's just a shortcut to save the
user from repeatedly setting individual packages to "update".

The typical use case is something like this:

You look at a list with packages you are interested in. Say, all YaST
packages, or all KDE packages. You might have used the "Search" filter view.

Then you realize that there are newer packages. You want to update all your
YaST or KDE packages. You use the context menu and select "All in this
list -> update, if newer version available"

Note: It doesn't say _anywhere_ that it will update to the most recent
version. This discussion is moot. It simply sets the status to "update" -
whatever the lib back-end does then.

All the UI algorithm does is to check if a package selectable has a newer
candidate. If it has, the status of this selectable is set to "update". This
is the same as the user manually going through the list and setting all
packages manually to "update" that have a newer candidate (i.e., those that
were displayed in blue font color in the old package selector).

Please note that there are list actions like this for all other possible
selectable states ("Install", "Keep", "Delete", "Taboo", "Protected", "Don't
install"). And there is also "Update unconditionally" which simply sets each
package to "update", no matter if there is something to update to. Since this
doesn't make sense in most use cases, we introduced that "update, if newer
version is available".

And of course there is the usual solver run afterwards if "auto check" is
enabled or when the user hits "check" or when the user is about to leave the
package selector with "accept". Business as usual.

I really don't understand what this discussion is all about.

Stefan Hundhammer <sh@xxxxxxx> Penguin by conviction.
YaST2 Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Nürnberg, Germany
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups