SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
You can mix SuSE and Packman Libs. I should know, I did it, 3 times. So you sure can do it. All you have to do is remove the conflicts, uninstall the old junky xines, and install the new hotness from packman.
I suppose what I said is kind of leaning towards they aren't compatible to mix... but you dont' have to remove all SusE packages to get the ones from packman(updates) to work. Many other dependencies of those packages still work fine from SuSE. The only things I had to replace were the old libs, which means, you can't upgrade xinelibs with xinelibs from other sources. But since you are upgrading those anyway, you can remove them first.
It isn't a new Xine alone issue. From SuSE, the versions you will get won't have mp3, they will be stripped. They also won't support additional things and certain movie formats, If you don't care, you can use SuSE's as the upgraded(but stripped) libraries will be available as SuSE gets around to it. They are working constantly on new and updated packages, but they can't do them all at once. So they are behind in release of current upgrades.
no, you can't mix libs, you can mix parts of the software that do not interact directly e.g. front-ends:
xine-ui suse and rest of the xine from packman, or xine-ui from packman and the rest from suse. That is prety obvious because dependencies are different.
Front-end does not care (xine-ui, Keffeine, and so on), but libs do.
He cant and should not try to install xine-lib together with packman xine libraries. This is a part of suse's xine package. His installation errors are typical and not supprising. If he wants xine-lib, then he needs to uninstall packman's xine and install SuSE's package. Of course, I dont see a point, because he is loosing functionality.
Go to this URL and follow their instructions. I used YaST to uninstall all DVD related aps from SuSE before installing these. They are all the current RPMs and specialize in making xine work. Unless German law changes SuSE's DVD application downloads will not support Hollywood DVD movies.
An easy way to resolve most SuSE dependency problems with rpms, is to install the 3rd party Smart Package Manager. Its available on the guru web site. Smart is compatible with YaST and APT (as long as you don't execute them at the same time, which is important). Then you do your package updates (for packages such as xine) using Smart.
I used to maintain complex lists of the various 3rd party multimedia, and which order to install them, etc ... to ensure my SuSE multimedia was "state of the art". After installing Smart, and watching it work, I threw out my lists. They are not needed and Smart looks after it for you.
Originally posted by broch looks like spam (smart installer). Not first thread, not first forum and not on topic
Not spam, and on topic. steffendenize has a host of dependency problems. YaST will not automatically sort them, only advise they exist. The Smart Package Manage will sort them, offering to download needed packages to fix the dependencies, after one click.
I used to spend hours sorting out dependencies. I used to maintain massive lists of dependencies to help me install various packages. No longer. I've tried apt, and yast, and they are both good, but they are a generation behind Smart.
The simple fact is the easiest way for steffendenize to sort out his dependencies, is probably to install Smart. ... Anyway, 'nuff said. Go ahead and call this spam, and stay in the dark ages, and help him manually sort out his dependencies, at a double the time it would take to install and run Smart. I won't waste this bandwidth, nor anyone elses time, by trying to offer positive suggestions on this thread. Clearly you prefer the manual method, and fair enough.
Last edited by void_linux; 11-05-2005 at 09:26 AM.
Ok, there seems to be a number of different suggestions to what I should do to solve the dependency conflict when trying to install the xine-libs. Either I should get a smart package manager or I should 'live' with the problems and do a manual work-around. Fair enough. I choose to do the manual work-around.
However, what I don't understand is that there is such a number of conflicts depending on which xine-lib you choose to install. What I read between the lines - correct me if I'm wrong - is that SUSE's xine-lib is 'bound' to the SUSE distro and that xine-lib (from xine on sourceforge) is distro independent? Am I getting this right? Is that the way it functions with all linux distros? That there is a number of conflict with software not installed using the 'package manager' that is integrated with the distro in question.
Pretty wierd thing as I would expect any distro to be able to use any software released under the open-software policy, hereunder the xine-lib directly from xine, and not necessarily waiting to SUSE to integrate it with their distros.
You nailed it. And you are right as well, it should be cross platform, but there are things some distros do to various packages, like KDE, xine, and others, to customize them, or make them legal to release with their free versions. WHich means in order to gain additional features, you need to know which version you want... the generic, or the one for your distro.