Hi Fox! Using software compiled from source and using yast to maintain packages will get you in serious trouble IMHO. The only way to have both is: Build your software from sources and make RPM's out of them which you then can install via rpm (yast, etc). You can use software like krpmbuilder to make this job a little simpler. Another solution especially for KDE 3.1 is: Keep calm and wait for the SuSE RPMs which are released shortly after KDE releases 3.1. This cannot last very long. After KDE releases 3.1, watch ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_8.1/ or one of its mirrors. Daniel Am Freitag, 17. Januar 2003 05:30 schrieb SLVRFX@flash.net:
KDE.org has recently released version 3.1rc6. I'd like to upgrade my default installation of KDE in SuSE Linux 8.1 Professional to the release candidate. This requires updating the Qt libraries as well to version 3.1.1. I can successfully configure/compile the source for the Qt library, but I'm confused about maintaining the RPM database. Even after I execute the 'make install' and my new Qt is installed, YaST still registers version 3.0.5 in the RPM database. I realize building Qt from the sources has nothing to do with the RPM database and that checkinstall can assist in creating an RPM package, but what kind of other conflicts will I be creating if I ever want to use YaST again to install software from the CD's? The same question applies for KDE 3.1rc6 (configure/compile OK, what about the RPM database)? Any suggestions on a 'proper' way to do this? Though SuSE produces some very stable packages, I would like to attempt the upgrade myself, therefore, updating from the sources would be great.
Thanks to all who can assist,
Fox