> 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 --it doesn't
> always work, but would be much better in the long run.
> >
Ah, I see. I never though of that. Thanks!
> >> 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).
> >>
> >
> >But isn't the whole purpose of upgrading to overwrite the current
> >installation?
> >I always point my upgrades to /usr in a deliberate attempt to
> >overwrite/ugprade (i.e. ./configure --prefix=/usr).
>
> If you are going to upgrade like that, then you should make sure that you
> have a backup of the entire /usr before you compile kde from scratch.
This
> way, if something goes wrong, it is much easier to restore the system to
> whatever condition it was in prior to the compile.
>
Yes, looking back I definitely should have backed up but naturally didn't :)
Still, doesn't RPM get confused if I just rudely overwrite KDE 2.0 with KDE
2.1 source?
Thanks again,
George
