On Sun, Feb 17, 2008 at 10:43:54AM +0100, Stephan Kulow wrote:

Am Freitag, 15. Februar 2008 schrieb Klaus Kaempf:

...

* Stefan Schubert [Feb 15. 2008 12:17]:

...

Ma ( We have too many Michaels in the team, so I take the login name

:-) ) has suggested to delete not supported packages if they have

unfulfilled dependencies only (Not regarding the vendors anymore). This list should be shown to the user who can decide how to go on.

From previous discussions of this topic (iirc, there's also a FATE entry for this), this seems to be the best approach.

+ I'm maintaining a list of packages that we know are dropped. So far we do not know though how to store the list. But it should be a property of the product that it's only complete if e.g. gcc41 is deleted.

product:opensuse recommends pattern:old-must-out which conflicts with gcc41 and other packages? -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org

Stephan Kulow schrieb:

Am Montag 18 Februar 2008 schrieb Martin Vidner:

...

product:opensuse recommends pattern:old-must-out which conflicts with gcc41 and other packages?

The recommend will be ignored if it creates conflicts...

There are several ways to create conflicts, but then the solver will give you: Solution 1: do not install old-must-out Solution 2: remove gcc41 remove ... remove ...

And if you want to keep gcc41, you have to keep everything. So to support a good upgrade, we need some more UI support I'm afraid.

Greetings, Stephan

The UI output in the update section of the Proposal frame should be like: These packages will not work on your updated system anymore. Therefore they will be deleted: - package a - package b The user can accept this or can go to the single selection in order to change these settings. I assume that we can generate this list by analyzing the problem list of solver and setting the concerning solutions. Greetings Stefan -- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi@suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org

Lukas Ocilka schrieb:

Stefan Schubert napsal(a):

...

The UI output in the update section of the Proposal frame should be like:

These packages will not work on your updated system anymore. Therefore they will be deleted: - package a - package b

I don't agree on filling up the upgrade proposal with dozens of packages. The number of packages going to be deleted is the maximum that proposal can stand.

...

The user can accept this or can go to the single selection in order to change these settings.

I assume that we can generate this list by analyzing the problem list of solver and setting the concerning solutions.

The list (if needed) should be visible in the detailed "Upgrade summary" in the package selector.

Bye Lukas

We already have an interface for it: problematicUpdateItems() which returns a list of items. This list includes items which will be dropped or for which there is no update available cause they have another vendor than the new available update item. I think we can use this list. Any other opinions ? Greetings Stefan -- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi@suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org

Lukas Ocilka schrieb:

Stefan Schubert napsal(a):

...

Lukas Ocilka schrieb:

...

Stefan Schubert napsal(a):

...

The UI output in the update section of the Proposal frame should be like:

These packages will not work on your updated system anymore. Therefore they will be deleted: - package a - package b

I don't agree on filling up the upgrade proposal with dozens of packages. The number of packages going to be deleted is the maximum that proposal can stand.

...

The user can accept this or can go to the single selection in order to change these settings.

I assume that we can generate this list by analyzing the problem list of solver and setting the concerning solutions.

The list (if needed) should be visible in the detailed "Upgrade summary" in the package selector.

We already have an interface for it: problematicUpdateItems() which returns a list of items. This list includes items which will be dropped or for which there is no update available cause they have another vendor than the new available update item. I think we can use this list.

Any other opinions ?

This list is used inside a package manager details when upgrading the system. Upgrade proposal only says: there are some issues that need your decision, see the details.

The idea sounds good to me :)

Lukas

I have implemented it now. Greetings Stefan -- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi@suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org

Klaus Kaempf wrote:

No, except that the list should be replaced by an iterator. ;-)

If the list is a reference to an internal list, you can still iterate it cheaply if you don't copy it :-) (I am not sure if this is the case) Duncan -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org