You should always try rpm -Fvh first. It will update RPM's already on the
system. There are several instances where you must use the --force with
Uvh however. If the RPM you're trying to replace is a different version,
as in another vendor's binary RPM, then sometimes RPM can't figure out
that the dependancies are actually met, so you MUST --force it because
--nodeps won't work most of the time in this situation. If you can use
Fvh, then so be it, but I know for a fact that both Red-Carpet and up2date
use --force when needed.
--
Austin Gonyou
Systems Architect
Coremetrics, Inc.
Phone: 512-796-9023
email: [EMAIL PROTECTED]
On Tue, 17 Apr 2001, Federico Mena Quintero wrote:
> "Michael Leone" <[EMAIL PROTECTED]> writes:
>
> > I suppose you could try a rpm -Uvh --force *.rpm.
>
> Do not do that. Ever.
>
> If you do that, you don't know what you are doing.
>
> You are fucking up the consistency of your dependency graph.
>
> Federico
>
> _______________________________________________
> evolution maillist - [EMAIL PROTECTED]
> http://lists.helixcode.com/mailman/listinfo/evolution
>
_______________________________________________
evolution maillist - [EMAIL PROTECTED]
http://lists.helixcode.com/mailman/listinfo/evolution
