<html>
<head>
</head>
<body>
<br>
<br>
Amir Tal wrote:<br>
<blockquote type="cite" cite="mid:200204131228.54793.tal@whatsup.org.il">
<pre wrap="">On Saturday 13 April 2002 03:16, Christian Rudolph wrote:<br></pre>
<blockquote type="cite">
<pre wrap="">Hi all<br><br>Forgive the newbie question, but I have searched for an answer on<br>kde.org, and have not found one as yet.<br></pre>
</blockquote>
</blockquote>
<br>
Well, it is not an newbie issue. It is common behaviour lately in the OpenLicense
world. Those who write software just think that they are half-gods because
of that and they do not write down the manuals and they do not respond to
common questions. I do not want to be misunderstood - they are as if they
were sent by god - we have good deal of the best software on this world,
thanks to them (and I would really like to contribute if it was not for my
work and family reponsibilities and playing with my band, of course). Just
the same behaviour I know from my wife - if she chose to set up the flat,
I was responsible because she would be tired after that. As if everybody
on this world shoud read every line of the OpenLicense source code to know
how it behaves - that could be on the OL developers' minds, maybe !<br>
<br>
OK, some basics first:<br>
<br>
1. KDE3 is NOT upgrade to neither KDE1 or KDE2 as the KDE2 was not upgrade
to KDE1. They are all standalone applications - that is WindowManagers, as
is WIN32, as is GNOME, as is FWMxyzwhatever. What this means - you install
it, patch some system startup scripts AND NOTHING DEINSTALL !!!!<br>
2. The --force --nodeps rpm options are the biggest lies I ever heard on
this world. And somebody (KDE.org also) should stop with this right now !!
If you do not know what you are doing you mess your sistem. Quite the same
is with the Amir's response - he achieved the working system through the
rpm -e ... and rpm ... --force --nodeps ... sequence because he just installed
nearly complete distro previously and has all dependencies working anyway.
But much of the Linux users have installed only what they need, due to the
old hardware and small disks. And most times not the newest distros.<br>
<br>
So what if you have the pre glibc2.2.x distribution (kernel 2.4.x) ? The
naming of the packages (RPM database) changed with that moment. You get glibc
package instead of the shlibs etc. etc. etc. You have to be very careful
at what you are doing with the installation of the software which is meant
for newest systems.<br>
<br>
Now, the correct installing sequence:<br>
<br>
1. Have your distro's CD very very near (or FTP/HTTP access to rpmfind.net
or your distro's home page)<br>
<br>
2. Start installing new KDE with the kdelibs package rpm -ivv --test kdelibsXXXXXX
- you will get the dependency request for the qt and the bunch others. The
--test option is safe. You do nothing to your system and you see what the
operation requires. The -vv option just displays everything through the process.<br>
<br>
3. You install qt with the rpm -ivh (probably without problems and dependencies).
In your case, you could easily add the --force for the qt install except
you are developer and you need qt2 development enviroment.<br>
<br>
4. You should search and install requested dependencies - missing packages
(which are not the part of the KDE installation) and all the dependecies'
dependencies from the available resources (CD, ftp.<somedistrohome>.../pub/...<version>.../,
rpmfind.net)<br>
<br>
5. Do not be scared to use the newest versions of those packages even if
you found them on the distro's version tree much newer than is yours. You
should only be carefull not to install glibc2.2 based packages if you do
not have glibc2.2 on your system. Such packages warn you about that during
the try, anyway.<br>
<br>
6. If you get the message as it was in your case (conflicts of certain files)
you should think about what it really means. In your case there is the question
if you are developer and if you really need the qt2 development system (maybe
it is supported by qt3 anyway, I am not quite sure) AND AFTER THINKING IT
CAREFULLY OUT YOU ISSUE THE --force OPTION. I, personally, had to install
KDE2 on the SuSE6.4 and nothing really broke through all the processes. There
could really be some dependency packages names changes but with the help
of the internet and rpmfind.net you really sort it out in your head first
and in your system afterwards. You will learn a lot during the process, which
is wrong, maybe, from your point of view, but not wrong from the UNIX administrator's
point of view (which you are as soon as you are installing the sistem issues
as is the desktop). UNIX is not Windows for Secretaries. It is like you own
and use the HarleyDavidson instead taking the TAXI everytime you needed the
ride - you should know every part of the system to be satisfied.<br>
<br>
7. Take your time and go through one package after another. It took me about
8 hours to KDE1->KDE2<br>
<br>
8. No need to install all and every single KDE package. You need:<br>
kdelibs to run KDE applications on any WindowManager<br>
kdebase to have running KDE WindowManager. If you use KDE apps on GNOME,
you do not need kdebase unless requested by the application's rpm.<br>
Afterwards it is really your choice what to install and what not.<br>
<br>
9. You add the path to the newly installed <KDEroot>/bin directory
to the /etc/profile just before the old KDE's bin path (and be sure you have
saved the old profile). The KDE apps would run now on any WM you have installed.<br>
<br>
10. You add the entry for the new KDE into the system startup script that
previously ran the old KDE or any other WM (on SuSE it is the /etc/rc.d/xdm
script). This entry normally points to the <KDEroot>/bin/kdm (and be
sure to have saved the old script). If you will not run the KDE WM, you skip
this patch.<br>
<br>
11. If you have the central system-enviroment-variables-file as is the SuSE's
/etc/rc.config, you make appropriate changes to it also (just save the old
one before you patch it). Again you skip this patch if you will not run the
newly installed KDE WM.<br>
<br>
12. The KDE would run after that. If you upgraded from KDE1 to KDE2 you should
consider to install XFree86 4.x to get the new kind of the font support and
the bunch of the new locales and keyboards. If you do KDE2->KDE3 you already
have XFree86-4.x installed. You can consider to install XFree86 4.2 if you
have glibc-2.2 installed otherwise you have to stick with the 4.1 version.
You should only disable the klipper to get the reasonable desktop speed.
Otherwise it really sucks (at least on my 500MHz Celeron).<br>
<br>
13. Only after you have unsuccessfully gone through all I have wrote, you
consider to upgrade/install newest distro.<br>
<br>
<br>
Good luck !<br>
<br>
<blockquote type="cite" cite="mid:200204131228.54793.tal@whatsup.org.il">
<blockquote type="cite">
<pre wrap="">I currently run KDE 2.2.2 on RedHat 7.2(Enigma) with all relevant<br>updates.<br>I have download all of the RPMs into a single directory under my<br>home directory. I have followed the instructions on the web site<br>for adding packages (as root), and receive conflict warnings while<br>attempting to install qt packages.<br><br><br>[root@delicje kde3]# rpm -ivh qt-devel-3.0.3-5.i386.rpm<br>Preparing... ###########################################<br>[100%]<br>file /etc/profile.d/qt.csh from install of qt-devel-3.0.3-5 conflicts<br>with file from package qt-devel-2.3.1-5<br>file /etc/profile.d/qt.sh from install of qt-devel-3.0.3-5 conflicts<br>with file from package qt-devel-2.3.1-5<br>file /usr/bin/findtr from install of qt-devel-3.0.3-5 conflicts with<br>file from package qt-devel-2.3.1-5<br>file /usr/bin/moc from install of qt-devel-3.0.3-5 conflicts with file<br>from package qt-devel-2.3.1-5<br>file /usr/bin/qt20fix from install of qt-d
evel-3.0.3-5 conflicts with<br>file from package qt-devel-2.3.1-5<br>file /usr/bin/qtrename140 from install of qt-devel-3.0.3-5 conflicts<br>with file from package qt-devel-2.3.1-5<br>file /usr/bin/uic from install of qt-devel-3.0.3-5 conflicts with file<br>from package qt-devel-2.3.1-5<br><br>Must I remove existing KDE 2.2.2 packages before installing 3.0?<br>If so, how?<br></pre>
</blockquote>
<pre wrap=""><!----><br>remove your old kde packages by rpm -e *kde or use the upgrade feature.<br>i did rpm -Uvh --force(for replacing old file) --nodeps , and it workied fine.<br>that was done without uninstalling 2.2.2 .<br>i am also using Enigma.<br><br>tal.<br><br><br></pre>
<blockquote type="cite">
<pre wrap="">Any advice or suggestions would be helpful.<br>Thanks in advance.<br><br>-Christian<br><br><br>___________________________________________________<br>This message is from the kde mailing list.<br>Account management: <a class="moz-txt-link-freetext" href="http://mail.kde.org/mailman/listinfo/kde">http://mail.kde.org/mailman/listinfo/kde</a>.<br>Archives: <a class="moz-txt-link-freetext" href="http://lists.kde.org/">http://lists.kde.org/</a>.<br>More info: <a class="moz-txt-link-freetext" href="http://www.kde.org/faq.html">http://www.kde.org/faq.html</a>.<br></pre>
</blockquote>
<pre wrap=""><!----><br></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="$mailwrapcol">--
---------------------------------------
Iztok Kobal
Ul. koroškega bat. 1
1231 Lj.-Èrnuèe
tel.,fax +386 (0)1 561 86 10
e-mail <a class="moz-txt-link-abbreviated" href="mailto:iztok.kobal@telemach.net">iztok.kobal@telemach.net</a>
e-mail <a class="moz-txt-link-abbreviated" href="mailto:iztok.kobal@siol.net">iztok.kobal@siol.net</a>
cellular +386 (0)31 264 965
---------------------------------------</pre>
<br>
</body>
</html>
___________________________________________________
This message is from the kde mailing list.
Account management: http://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.