Re: Upgrading from RPM to SOURCE

["Hall" <dhs erinet com>]

I personally think mixing RPMs and source packages is bad... It can be done
though.

When installing RPMs that require other packages, it may complain about some
packages not being installed (actually, not having the RPM package installed
and registered in the RPM database). In that case, I *think* it's safe to
add the "--nodeps" (or is it "--force" or both???) to the RPM command.

In your case where you're switching from RPMs to the source packages, yes,
you do have to remove the existing RPM packages.

Another issue with source packages and RPM packages is that, again I think
this is the case, they install to different locations. Therefore, you may
likely end up with two copies of the programs or possibly old versions of
lib files in one place and the newer ones in another. And guess what, when
another program checks for that lib, it will certainly find the old one!!
;-)

Good luck,
Hall

----- Original Message -----
From: Nathan Clegg <nathan@islanddata.com>
To: <gnome-list@gnome.org>
Sent: Monday, April 12, 1999 12:30 PM
Subject: Upgrading from RPM to SOURCE


> I installed all of gnome through the RedHat 5.2 RPM instructions.  I am
> now interested in getting the latest and greatest and don't want to wait
> for/be dependent on new RPMs.  Gnome is actually the first thing I have
> ever installed with RPMs anyway (but boy was it a breeze).
>
> Anyway, the question is whether I should remove the RPMs before installing
> the new stuff or if I should just install the new from source and ignore
> the RPM versioning.  Also, anything I should be worred about upgrading
> together?  I don't want gnome to die on me with incompatibilities.  Here's
<snip>