Hi, As we support now zypper dup as official distribution upgrade, there is one issue I would like to see solved: zypper dup leaving unsupported packages behind. There are 2 cases where it's obvious: - we dropped support for kfoobar as it will only crash with newer KDE, so it should be removed even if it it's still able to keep it for the solver - we have tons of old shared libraries that should be removed unless they are required by some package not from openSUSE (or that package is locked) Yast will get a list of such packages from control.xml, but zypper dup has no real access to that file and I don't want to maintain it twice actually. So I brainstormed with the two Michaels (one after the other :) and what came out of this was the following concept: The distribution algorithm will do the following before going into the solver: - check what installed packages provide products - estimate the update candidate (newest package with the same name) - of this package, check all provides with namespace weakremover (I'm open for suggestions on a better name :) - with this list of provides, create weak delete requests for all installed packages that match the name and the vendor of the package providing the product Means, openSUSE-release-11.1 is installed and provides product(openSUSE). Now zypper dup would update to openSUSE-release-11.2, but before it does that, it will check the weakremover provides of said openSUSE-release and weak delete gcc43 because openSUSE-release-11.2 provides weakremover(gcc43). Any better idea that can be implemented in a reasonable time? I know that this is kind of ugly, but I don't see any better solution atm. Putting things in the meta data is something that I see as too late now ;( Greetings, Stephan -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org