Anybody else try the KDE 3.1 Beta-2? WARNING!
SuSE did not provide a kdenetwork RPM. That broke my kmail. I ended up downloading the tarballs for kdelib, kdebase, and kdenetwork source code. I found I had to do a tar xvjf tarball.tar.bz2 \ cd tarball export QTDIR=/usr/lib/qt3 \ export KDEDIR=/opt/kde3 \ cvs update \ make -f Makefile.cvs \ ./configure \ make && make install on each tarball. I also had to install a few development rpms to make it work. I don't recall which ones right now. I also ran ldconfig after each install, but I'm not sure I needed to. I'm going off of memeory on the above so YMMV. http://dot.kde.org/1033624198/ STH
On Friday 04 October 2002 15.44, Steven T. Hatton wrote:
SuSE did not provide a kdenetwork RPM. That broke my kmail. I ended up downloading the tarballs for kdelib, kdebase, and kdenetwork source code. I found I had to do a
tar xvjf tarball.tar.bz2 \ cd tarball export QTDIR=/usr/lib/qt3 \
export KDEDIR=/opt/kde3 \
Whoa. This will overwrite the kde 3.0.3 installation. I'm not sure you want to do this when testing a beta. Better use something like KDEDIR=/opt/kde3-beta or something. Also, replace all instances of "\" with "hit enter" :)
cvs update \
erm, no.
make -f Makefile.cvs \
You only have to do this when installing from cvs, not the packaged tarballs. The tarballs already have the automake/autoconf stuff ready for use. //Anders -- 'Deserves [death]. I daresay he does. Many that live deserve death. And some that die deserve life. Can you give it to them? Then do not be too eager to deal out death in judgement. For even the very wise cannot see all ends.' --Tolkien, The Lord of the Rings
On Friday 04 October 2002 09:50 am, Anders Johansson wrote:
On Friday 04 October 2002 15.44, Steven T. Hatton wrote:
SuSE did not provide a kdenetwork RPM. That broke my kmail. I ended up downloading the tarballs for kdelib, kdebase, and kdenetwork source code. I found I had to do a
tar xvjf tarball.tar.bz2 \ cd tarball export QTDIR=/usr/lib/qt3 \
export KDEDIR=/opt/kde3 \
Whoa. This will overwrite the kde 3.0.3 installation. I'm not sure you want to do this when testing a beta. Better use something like KDEDIR=/opt/kde3-beta or something. Also, replace all instances of "\" with "hit enter" :)
I should have mentioned that, but it was too late for me. SuSE had already done that for me with the rpms :-/
cvs update \
erm, no.
make -f Makefile.cvs \
You only have to do this when installing from cvs, not the packaged tarballs. The tarballs already have the automake/autoconf stuff ready for use.
That's what I thought too. It didn't work for me.
//Anders -- 'Deserves [death]. I daresay he does. Many that live deserve death. And some that die deserve life. Can you give it to them? Then do not be too eager to deal out death in judgement. For even the very wise cannot see all ends.' --Tolkien, The Lord of the Rings
Whoa. This will overwrite the kde 3.0.3 installation. I'm not sure you want to do this when testing a beta. Better use something like KDEDIR=/opt/kde3-beta or something. Also, replace all instances of "\" with "hit enter" :)
I should have mentioned that, but it was too late for me. SuSE had already done that for me with the rpms :-/
The SuSE 3.1-beta rpms overwrite kde3.0.3? Ugh, that's not nice of them.
cvs update \
erm, no.
make -f Makefile.cvs \
You only have to do this when installing from cvs, not the packaged tarballs. The tarballs already have the automake/autoconf stuff ready for use.
That's what I thought too. It didn't work for me.
Probably because you did the cvs update, but if you want to use the latest cvs you need to add a step export CVSROOT=:pserver:anonymous@anoncvs.kde.org:/home/kde otherwise "cvs update" will give an error about not having a CVSROOT specified. //Anders
On Friday 04 October 2002 10:02 am, Anders Johansson wrote:
Whoa. This will overwrite the kde 3.0.3 installation. I'm not sure you want to do this when testing a beta. Better use something like KDEDIR=/opt/kde3-beta or something. Also, replace all instances of "\" with "hit enter" :)
I should have mentioned that, but it was too late for me. SuSE had already done that for me with the rpms :-/
The SuSE 3.1-beta rpms overwrite kde3.0.3? Ugh, that's not nice of them.
That's what I thought too.
cvs update \
erm, no.
make -f Makefile.cvs \
You only have to do this when installing from cvs, not the packaged tarballs. The tarballs already have the automake/autoconf stuff ready for use.
That's what I thought too. It didn't work for me.
Probably because you did the cvs update, but if you want to use the latest cvs you need to add a step
I did the cvs update after I had problems. I believe the problem was something about not having a configure.h.in, or something.
export CVSROOT=:pserver:anonymous@anoncvs.kde.org:/home/kde
That's what I thought too, but just for grins, I typed cvs update, and it ran. There is still no entry for the kde cvs server in my .cvsrc or .cvspass.
otherwise "cvs update" will give an error about not having a CVSROOT specified.
That's what I thought too. Don't ask me why it worked the way it did. <shrug>
//Anders
participants (2)
-
Anders Johansson -
Steven T. Hatton