Upgrading KDE from kde.org sources...
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
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
On Friday 17 January 2003 05:40, Daniel Eckl wrote:
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).
Yes, this would be the Right Way. So, wait, until SuSE has the rpm's for KDE-3.1 ready and install those. But: there's a 3rd way that I like to add: http://konsole.kde.org/konstruct/ This is a kind of "Fancy Makefile System", and will download, compile, and install kde (currently: kde-3.1-rc6) for you, together with a lot of bells and wistles - if you want. I installed kde-3.1-rc6 in my home directory (~/kde-3.1-rc6) and use this little script to start it on the 2nd graphical console <ctrl>-<alt>+<f8>: ----<kdetest>--- #! /bin/bash KDE_VER="kde3.1-rc6" export QTDIR="$HOME/$KDE_VER" export KDEDIR="$HOME/$KDE_VER" export LD_LIBRARY_PATH="$KDEDIR/lib" export PATH="$KDEDIR/bin:$PATH" export KDEHOME="$HOME/.kdetest" WINDOWMANAGER="$KDEDIR/bin/startkde" startx -- :1 ----<kdetest>--- If the rpm's of kde-3.1 come out, I'll remove ~/kde-3.1-rc6, rename ~/.kdetest to .kde and install the rpm's. Cheers, Leen
Hey Leen, that's a nice posting - i am looking for hints like that for a while now. I want to add that I just compiled qt 3.1.1 in /usr/local/qt-3.1.1/ with QTDIR=/usr/local/qt-3.1.1 and my special Pentium4 flags (-march=pentium4 -O3 -fomit-frame-pointer) set for gcc (have to modify a file in ./mkspecs/ subdir). For ./configure use -thread and enable gif support (see ./configure --help). Then I linked /usr/lib/qt3 to /usr/local/qt3 and made an 'ldconfig'. On the next start of SuSE KDE 3.0.5 the system uses qt-3.1.1 optimized for my CPU. I don't experienced any problems - but a slight improve in performance (i can not measure it, just 'feeling'). This is why i do not like SuSEs rpms - they are optimized for Pentium1 but with backward compatibilty to x486. The next steps should be: - compiling of KDE 3.1, gfx libraries and Freetype with P4 optimization (anything else is worth recompilng?) - give it a try with Intels icc (should improve P4 speed up to 100% over gcc) Who has any experiences or hints for that? Cheers, Tim On Friday 17 January 2003 08:19, Leendert Meyer wrote:
On Friday 17 January 2003 05:40, Daniel Eckl wrote:
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).
Yes, this would be the Right Way. So, wait, until SuSE has the rpm's for KDE-3.1 ready and install those.
But: there's a 3rd way that I like to add:
http://konsole.kde.org/konstruct/
This is a kind of "Fancy Makefile System", and will download, compile, and install kde (currently: kde-3.1-rc6) for you, together with a lot of bells and wistles - if you want.
I installed kde-3.1-rc6 in my home directory (~/kde-3.1-rc6) and use this little script to start it on the 2nd graphical console <ctrl>-<alt>+<f8>:
----<kdetest>--- #! /bin/bash
KDE_VER="kde3.1-rc6"
export QTDIR="$HOME/$KDE_VER" export KDEDIR="$HOME/$KDE_VER"
export LD_LIBRARY_PATH="$KDEDIR/lib" export PATH="$KDEDIR/bin:$PATH"
export KDEHOME="$HOME/.kdetest"
WINDOWMANAGER="$KDEDIR/bin/startkde" startx -- :1 ----<kdetest>---
If the rpm's of kde-3.1 come out, I'll remove ~/kde-3.1-rc6, rename ~/.kdetest to .kde and install the rpm's.
Cheers,
Leen
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
Am Freitag, 17. Januar 2003 13:57 schrieb Slvrfx:
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?
I think there's no problem if you install a little application from sources, if you cannot / don't want to get an rpm. Problems only show up, if you update an application from sources that: 1. have an older version installed via rpm 2. any other rpm package searches for this app as prerequisite. Example: You build the vorbis libraries on your own and install them. Will work fine. If you then install an RPM that depends on libvorbis, it perhaps will say that libvorbis.so.0 is not installed (but it is). Then you can install that other rpm with --nodeps, but I don't know what yast will say after that. There could be shown an (not existing) dependency fault. Daniel
Hello,
From: slvrfx@flash.net [mailto:SLVRFX@flash.net]
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
When I compiled apps myself using SuSE I used checkinstall. Once installed you use it instead of make install. It bundles the compiled files into an rpm and then installs it, so you still have a consistent rpm database and you can use your selfmade rpm to reinstall if needed. Christian
Hi Christian! That sounds interesting. Do you mean this program? http://asic-linux.com.mx/~izto/checkinstall/ Daniel Am Freitag, 17. Januar 2003 14:03 schrieb Christian Herzyk:
Hello,
From: slvrfx@flash.net [mailto:SLVRFX@flash.net]
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
When I compiled apps myself using SuSE I used checkinstall. Once installed you use it instead of make install. It bundles the compiled files into an rpm and then installs it, so you still have a consistent rpm database and you can use your selfmade rpm to reinstall if needed.
Christian
Hi,
From: Daniel Eckl [mailto:daniel.eckl@gmx.de]
Hi Christian!
That sounds interesting. Do you mean this program? http://asic-linux.com.mx/~izto/checkinstall/
Not sure, but I think so. You should find it on your SuSE CDs also. Christian
Thanks for the information Christain. And yes I have used checkinstall for
smaller applications like K3B, but it doesn't really work on packages like
Qt and KDE since SuSE also builds the -devel -doc -examples packages and
checkinstall does not.
Thanks again to everyone.
----- Original Message -----
From: "Christian Herzyk"
Hello,
From: slvrfx@flash.net [mailto:SLVRFX@flash.net]
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
When I compiled apps myself using SuSE I used checkinstall. Once installed you use it instead of make install. It bundles the compiled files into an rpm and then installs it, so you still have a consistent rpm database and you can use your selfmade rpm to reinstall if needed.
Christian
-- 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
participants (6)
-
Christian Herzyk
-
Daniel Eckl
-
Leendert Meyer
-
Slvrfx
-
slvrfx@flash.net
-
Tim Ruehsen