> I'm trying to install Kde 3.0 but I can't.
> I downloaded all MDK files from:
> ftp.unina.it/pub/Unix/KDE/stable/3.0/Mandrake/8.2/RPMS/i586

I upgraded to 3.0 final last night, but I already had 3.0 beta
2 installed, so maybe that's cheating :).

The install went fairly straight forward, although there were
a few gotchas. I use Mandrake 8.1, but the installation for that
shouldn't vary much from doing it on 8.2. If you are upgrading from
2.2.x or installing kde 3.0 for the first time, that may be 
different.

What I recommend doing after you've ftp'd down everything in the
kde subdirectory off of ftp.kde.org - is to start upgrading the
lower level components first before installing or upgrading the
big major components such as kdebase. This helps dependency 
conflicts. 

That's the approach I took this time around and there were
still some dependency issues - iirc I had to a --nodeps install
on koffice, because it wanted a kdegraphics rpm and my
rpms were kdegraphics3. Minor spelling diff, but it makes a
difference to RPM.

By lower level stuff I mean things like libxslt, libcups, 
etc. Similar titled libraries and their base packages (for
example cups* and libcups*) depend on each other; you'll be
better off if you install the library components first.

Once those are installed, then install libqt*. The -devel
packages depend on their base packages - for instance kdelibs,
and kdelibs-devel. Install them in pairs on the RPM command
line, like

# rpm -Uvh kdelibs-3.0.0-1mdk.i586.rpm kdelibs-devel-3.0.0-1mdk.i586.rpm

Next, if you get dependency errors from another package, suich as
kdearts needing kdelibs, or what have you, hit your up arrow button
which will give you the last command entered, then add the RPM its
asking for. Keep adding RPMS on the command line (but just the ones
it needs) until all dependencies are satisfied. If I remember 
from last nights install, I had to do this about 3-4 times just to
make sure everything got upgraded correctly.

In some cases you'll need to get rid of an older RPM before the
new RPM can be installed. Mostly this is needed if you get
file conflicts (like somesuch file in foo-1.rpm conflicts with
the same file in foo-2.rpm).

> Um abra�o,
> L�cio Costa

Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to