I installed KDE 3.1.1 rpms on two different boxes without any major problems.
I had to download couple of additional rpms from http://rpmfind.net : 1. pcre-devel-3.9-5.i386.rpm 2. glut-3.7-8.i386.rpm I installed these two first. then installed all the KDE rpms including qt's. If you have LISa installed you may want to uninstall it before installing the new kdenetwork rpms. I did not install kdeaddons; it required libmad.so.0. I installed libmad.so.0 first then tried to install kdeaddons but it would still say that it needed libmad.so.0. This was the only problem I had. One thing I noticed is that the Control Center has less features than KDE 3.0 Control Center. For example, the File Association module is missing from File Browsing category. The Font Manager is missing from System category. To make your desktop more attractive you can download nice themes from http://kde-look.org . I hate the default Red Hat BlueCurve. -Nash On Monday 24 March 2003 03:08 am, -ray wrote: > The rpms are probably broken. I've spent hours and hours trying to > resolve kde.org rpm dependencies in the past, to no avail. They are > circular, cross-linked, and stupid. I've always used this procedure, and > it works ok: uninstall all kde, arts, and qt rpms. Then install qt, > arts, and all kde rpms with --nodeps (and sometimes --replacefiles). If > that doesn't work, then plan B is uninstall everything, then install qt, > arts, and kde rpms from the distribution cd (and updates). Since kde > config is stored in ~/.kde, you shouldn't lose any setup info. That > should at least get you running again. > > --nodeps isn't always a bad idea, if you know what you're doing. For > instance, the whole XFree86 suite isn't needed if you'll just be tunneling > the display to another X server. Or if i'll only be playing ogg with > xmms, then there's no need for the xmms-mpg123 rpm dependency. Be > forewarned that things might not work perfectly when using --nodeps, but > it probably won't work perfectly anyway (haha), and --nodeps has come in > handy for me more times than not. > > -ray > > On 23 Mar 2003, Tim Fournet wrote: > > for future reference, you can pass wildcards to rpm on the command line. > > rpm -Uvh * > > will install every file in the current working directory. > > > > using --nodeps or --force with rpm creates instabilities, and in most > > cases is never a good idea to do. If you run across an rpm with > > unmeetable dependencies, chances are it's either broken or you haven't > > worked hard enough to solve dependences. Package management utilities > > such as up2date, apt, and yum work to make this easier by using package > > repositories that know how to get dependencies solved. > > > > -Tim > > _______________________________________________ > General mailing list > [email protected] > http://oxygen.nocdirect.com/mailman/listinfo/general_brlug.net
