Upgrading KDE.
 

Hello... sorry to bother but I think I need some help.
I'm running a Mandrake 10.1 Official distro and I'm trying to upgrade KDE 3.2 to the 3.4. What I know is I need to open the Source Manager and add the KDE ftp in it so I open the Source Manager, I choose ftp and I fill in the spaces with some fancy name and the path to the nearest ftp server:
(the site doesn't like me posting links but anyway it's on the KDE site it MUST be right!)
My computer then works a little, says it's downloading something and then comes out with a rather longish explanation why it couldn't complete the operation which begins like that: "it's impossible to retrieve the list of new packages...".
So how can I upgrade my KDE?

I've always had problems like that with mandrake i.e. urpmi works a dream if you're installing "mandrakised" rpms and the like, but if you then try someone elses, like one for fedora/redhat or maybe SuSE you end up with lots of missing dependencies.

It may be that you'll have to look at installing it from tar.gz files. Except I'd imagine that they will be lots of differents i.e. kdebase, etc etc - and the possible downside is that even if you manage to get the base package installed, you might also struggle everytime you try to get another facility (using gentoo, I learned that kde in toto, is 70+ different packages for everything, but I'd presume that you can "pick and choose" the ones that you want to use).

This location might be of some use, at least it seems to be a list of mandrakised rpms for kde 3.4 and even if you have to download the ones that you want individually, it's got to be worth a try ???

Sorry I can't be of more help.

regards

John

If you take a look in the Mandriva forum here, you will see that the general consenus of the Mandrake/mandriva users is that to install KDE3.4, you should really install it from source. There are currently no *official* mandrake rpms for it. Thac's rpms (in bigjohn's post) do not follow Mandrake's rules, and might break your system. Or they might not. But a lot of knowledgable folks installed them, then deleted them and reinstalled 3.2, and built 3.4 from source.

An alternative would be to get apt4rpm (also called aptrpm), a port of Debians apt-get to rpm-based Linux. Download three rpms (or .src.rpms and build for your box): lua, apt-libs, and apt. Install in that order, then use apt to get, install, maintain, update, and upgrade your system.
There is also a GUI frontend to apt called Synaptic, if you're more comfortable with the point-and-click rather than command-line operations.
There's a lot on the 'net about it. Use google to explore the topic, then decide whether or not to try it. It doesn't replace rpm; it's an adjunct to make up for the shortfalls of rpm. But (a very big but), apt and rpm seem made for each other. Perhaps in the not-too-distant future, we may see the two merged into one.
According to some opinions I've read, you should be able to do the same with urpmi.

I've finally decided to try the source but I can't figure out what does it want here:

*** No rule to make target `/usr/include/kbookmarknotifier.h', needed by `kbookmarknotifier.kidl'. Stop.

I was making kdebase-3.4.0.
Anybody has any idea?

P.S. I've already built kdelibs, arts and kdeadmin.

you need to upgrade qt first.followed by arts,kdelibs,and kdebase.these packages need to be installed in this order.after that it dosent matter.

Ok, great...
I've installed qt 3.3.4 from the sources but then when trying to configure kdebase-3.4.0 I get this error:

checking if UIC has KDE plugins available... no
configure: error: you need to install kdelibs first.

Now I have installed qt 3.3.4, arts 1.4.0 and kdelibs 3.4.0
Any clue?
Many thanks for your help!

kde base should be the next package.........after that the package order is unimportant.it's not even required to install all the remaining packages,i leave the internationalization one out all the time.

hmm...I've tried to install kdebase and I get the same result...gosh I'm beginning to feel depressed...

Ok folks I managed to solve the problem. Looks like qt 3.3.3 conflicted with qt 3.3.4 and I had to remove all the qt 3.3.3 and old kde 3.2 packages. Something of a suicide move, the non-return point at least but it worked...