Gang,

This relates to the other 2 posts I made with regards to loading MPlayer as well as trying to get a workable version of the xine/kaffeine stuff on my new build of SUSE 10.0 (full, official "retail" version).

After discovering that I could load and use MPlayer with no problems at all (downloaded from the "packman" website), some other users mentioned that I should be able to delete my current version of the xine/packages and reinstall them as well. This had been my original concern since I got a couple of dependency warnings when I first attempted to delete "xine-lib" from my system.

So, with this in mind, I thought I'd go ahead and delete the "xine-lib" package and proceed from there. Within Yast2, I displayed my installed packages and then selected "Video/Player" from the tree list. I then highlighted the "xine-lib" package entry, selected the "Autodetect" checkbox at the bottom of the GUI, and then chose the "Delete" option. Then I hit the "Accept" button at the bottom of the Yast2 GUI.

As expected, this caused the display of a popup GUI which gave some warnings about dependency; there was one message in the list that mentioned that "amarok" would be affected. Based upon the info I got from some others users, I used the little popup GUI to indicate that it would be OK to just delete amarok and proceed with removing xine-lib.

As SUSE took off from there, I watched the progress GUI window to see what was happening. It looked like everything was working OK, and then, much to my surprise, it looked like SUSE was automatically reloading the xine/kaffeine stuff, without my telling it to do so. From the info I saw being displayed, it looked like SUSE was automatically reloading the very files I intended to install *after* I finished deleting my current xine/kaffeine packages. Hmmm; interesting.

Anywho, to make a long story even longer, I let the procedure finish and I exited Yast2, just to see what was going on. The Kaffeine player was still an available option from the KDE "Multimedia/Video Player" GUI menu, so I kicked it off and see if it would play any of my video files. And it did! And so far, Kaffeine seems to be playing my video files with no problem, just as MPlayer is able to do.

But here's my concern : When I went back to Yast2 in order to get some sense of what had happened, I displayed the package info for the Multimedia/Video Player stuff once again. Almost all of the xine/kaffeine packages were still there, but there was now a little "Locked" icon displayed by each entry. I assume that this means Yast2 won't let me touch those packages right now. Even the MPlayer entry has this same "locked" icon displayed beside it, which is certainly something I did not anticipate. The only package entry in the list which is not currently loaded is "xine-lib", which is the package I was attempting to delete.

Would one of you kind souls tell me what has happened? Since both kaffeine & MPlayer seem to be fully functional so far (amarok is as well), this appears to be most of what I wanted to accomplish. But those little "locked" icons within Yast2 are of some concern to me, and I'm not sure if I need to do anything else at this point. From what I saw displayed from within Yast2, it looked like SUSE automatically loaded several packages in order to make the video/amarok stuff functional once again, including a couple that I was not familiar with (maybe these packages did something to initiate the automatic reload of the video packages).

Thanks very much for any advise some of you may offer. As long as all the video/audio stuff contines to work OK, I guess I shouldn't complain too much. But I really would like to know what has taken place and why those little "locked" icons are now being displayed within Yast2.

Don't worry about the "locked" symbols. YaST sets all third party packages to "locked" (so you should see this symbol for your mplayer rpm as well). This avoids to overwrite 3rd party packages in a YOU update.

I am not completely sure what happended in your case, but I would assume that you have successfully replaced the SUSE version of Xine with the version from packman. Those packages are named differently (SUSE=xine-lib, packman=libxine).

Hope this was helpful.

abisko,

Thanks a lot for the info you gave me; I'm gonna save it to a text file since it does help me to understand how SUSE does certain things.

And I was curious why there was that particular difference in package names (i.e., "xine-lib" vs. "libxine"). Thanks for clearing that up. Those are the types of simple details that help us all better understand how our SUSE OS software works.

I guess the only remaining "curiosity" concerns the mechanism of why SUSE automatically updated those packages that I had intended on doing myself (libxine, xine-ui, kaffeine, etc.). As soon as I gave Yast2 the "green light" to delete my existing "xine-lib" package, it soon responded with its auto-update action. Like most users, that's perfectly fine with me as long as everything works OK. :-))

I recently downloaded some Yast2 documentation from Novell, so I hope I can find out a bit more about when Yast2 will automatically download a package right after I've deleted something. It surprised me when it happened, but all the xine/kaffeine/amarok stuff seems to be working just fine so far.

Anywho, thanks very much for the clear and informative info. I've always learned some good stuff everytime I've visited this excellent website.

Have fun!