KDE4 The Transition in openSUSE 11.1
The purpose of this documentation is to describe the kde4 naming policy transition. And, in the event that you are updating kde4 to kde4.2.* or kde4.3.*, to help you put all the correct packages in place. Become familiar with Yast – Software Management and the filter options.
Select Filter: ImageBam - Fast, Free Image Hosting and Photo Sharing
System Filter: ImageBam - Fast, Free Image Hosting and Photo Sharing
Originally and with regular updates the majority of the kde4 packages for kde desktop applications (In our example we are using Amarok) have the prefix: kde4-package_name.
kde4-amarok: ImageBam - Fast, Free Image Hosting and Photo Sharing
New packages have had the kde4- prefix dropped. Therefore kde4-amarok becomes just: amarok. However, a prefix is now placed on kde3 packages, a point you should be aware of.
amarok: ImageBam - Fast, Free Image Hosting and Photo Sharing
kde3-amarok: ImageBam - Fast, Free Image Hosting and Photo Sharing
What Can Happen.
During the update process eg; If you are following this: KDE4.2.* (How To Add) Guide. - openSUSE Forums
You can become confused because of the name changes. This is heightened by the fact that now there are so many versions available and in the case of amarok there are also Packman version just for a good measure of confusion.
What to Do?
Think! One of the big clues is, if you view the repo’s by the ‘System’ filter (this shows every package you have installed in the .rpm database). Scroll the list. Blue text showing in the Version Number column is representing an available update. Red text here means either a Rollback or a defunct package. In the images above, the Versions Tab has been selected so you can see where a package is available from.
This image shows a package on my system that has no available sources (you see there are no radio buttons): ImageBam - Fast, Free Image Hosting and Photo Sharing
This is because this package is a manually installed .rpm and is not available in the repos. A few old kde4 packages end up like this. But mostly you are looking for the ones like in our example that have changed name.
The solution is not pretty, but remember you are dealing with repositories you have added that are not shipped with the original OS. Basically you are in the realms of testing and development. Effectively you have to find your way through it. It should quickly become obvious to you and all it requires is a little cross checking. It might seem scary, (You will have to mark some packages to delete) Eg; kde4-amarok and then select the amarok package from the Build Service repo you have. If you are doing a Update all in this List in the kde4 factory repo. In some cases the solver will see to this for you, mark the old kd4- package to delete and bring in the newer version, but NOT always. Remember repo priorities are important, see the 4.2 HowTo above.