I would say you'd be much better off if you found the 2.1 SRPMS and did a
rpm --rebuild, then installed the resulting rpms. I would not suggest
compiling from source unless there is a way to point it to /usr/local (such
that it wouldn't overwrite any existing information you have).
Michael
--
Michael Viron
Registered Linux User #81978
Senior Systems & Administration Consultant
Web Spinners, University of West Florida
At 12:27 AM 07/29/2001 +1000, [EMAIL PROTECTED] wrote:
>If, for instance, I have the KDE 2.0 packages (RPM, of course)
>installed...and I download the KDE 2.1 source code (instead of the RPMs),
>what should I do?
>
>Should I uninstall (rpm -e) the KDE 2.0 packages *before* compiling &
>installing the 2.1 source code (but then wouldn't any new app's RPMs
>designed
>for *only* KDE 2.1 and above, refuse to install because KDE 2.1 doesn't look
>like it's been installed, to the RPM program?)?
>
>Or can I just compile & install the 2.1 source over the RPMs (but wouldn't
>RPM get confused or annoyed?)?.
>
>I am asking these questions because some of my recent "upgrades" (including
>X
>4.0.3, xmms, KDE 2.2, sawfish etc.) have been exhibiting unusual behaviour,
>to say the least. These were installed by just overwriting the current
>installation and not telling RPM.
>
>Thanks,
>George
>
>
>
>
