If I should wait for SuSE to release software packages in RPM form, what
happens if I find a problem with a particular program and can't wait for
them to package it? Same goes for software SuSE does not package, how would
I install and maintain the RPM database? Should I just be reading the SuSE
.spec files and base my own packages on them?
----- Original Message -----
From: "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
-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e