On Sun, 29 Jul 2001 00:27, [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
Never overwrite an RPM installation with a tarball compilation. Uninstall the
old RPMs just before you run "make install".
You may want to have a look at CheckInstall
(http://mayams.net/~izto/checkinstall-en.html). This can install tarballs as
RPMS (so they can be manipulated just like any other RPM), and give you a
binary RPM file at the end. However, you should still uninstall the old RPMs
before you use this.
--
Sridhar Dhanapalan.
"There are two major products that come from Berkeley:
LSD and UNIX. We don't believe this to be a coincidence."
-- Jeremy S. Anderson
