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
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
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.
True, but what if only had the pure .tar.gz source code?
I would not suggest
compiling from source unless there is a way to point it to /usr/local
(such
that it
At 01:33 AM 07/29/2001 +1000, [EMAIL PROTECTED] wrote:
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.
True, but what if only had the pure .tar.gz source code?
In that case, you can try running rpm -t filename.tar.gz
At 01:33 AM 07/29/2001 +1000, [EMAIL PROTECTED] wrote:
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.
True, but what if only had the pure .tar.gz source code?
In that case, you can try running rpm -t
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
--
