SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I added 3 sites to my repositories for suse 10.2 and I am trying to install kstars. I am running ./configure and added the dependencies from yast like c compiler and X required for the program until I get this error:
in the prefix, you've chosen, are no KDE headers installed. This will fail.
I searched through the yast repositories and found nothing for it and searched the net and found this:
kdelibs3-devel-3.5.4-19.i586.rpm for suse 10.2.
Now because of that rpm, I have 21 extra dependecnies to take care of first.
My question is, did I pick the right rpm for this? Do I really have to go through all that depencencies crap to install a program?
the short answer is yes. In order to develop a kde program, you must have the kde development libraries, and all the development libraries that it depends on.
That's why I don't like developing with K. They use the 'everything but the kitchen sink' philosophy of making a desktop.
the short answer is yes. In order to develop a kde program, you must have the kde development libraries, and all the development libraries that it depends on.
That's why I don't like developing with K. They use the 'everything but the kitchen sink' philosophy of making a desktop.
I don't think you are entirely correct in your observation. If you install only the kdelibs devel packages, then you are not really installing all of the kde developement libraries. I suspect the extra dependencies are libraries, programs and other packages required for development and not necessarily kde related packages.
So reddazz, Will I need to install other dependencies required to install kdelibs3-devel-3.5.4-19.i586.rpm to take care of the kde header problem? Just want to make sure before I go through depencency hell. Thanks
So reddazz, Will I need to install other dependencies required to install kdelibs3-devel-3.5.4-19.i586.rpm to take care of the kde header problem? Just want to make sure before I go through depencency hell. Thanks
-bhert
Why would you go through dependency hell. Just install the kdelibs3-devel package using YAST and all dependencies will be automatically resolved. If you were using rpm at the command line, then you would need to manually install all the required dependencies before installing kdelibs3-devel, but there is not need for such hard work.
Thanks for the reply reddazz, I went to yast and couldn't figure out how to install kdelibs3-devel-3.5.4-19.i586.rpm that I downloaded to the hard drive, I could only see the source repositories. And of course the rpm is not in the list. Is there a way for yast to install software from the hard drive? Thanks
Just search in yast software management tool for kde and you will see kdelibs3-devel in the list. Select it for installation and all you should be good to go.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.