Uh, no, I know what dependancies are unresolved. This is very simple. If
you want to force an install, like I believe the guy was trying to do, you
can do the method below - BUT WHEN YOU ALREADY KNOW WHAT THE DEPS ARE!!
Also, If you think about it, if you try to install, say XFree. You do a
rpm -Uhv *.rpm in the directory you have all your recently downloaded
packages. Well, you are going to fail dependancies on packages that you
will eventully install anyway, further down the list. So, once you check
all the deps, and are sure you have all the packages, you can force them
(remember, beta and cooker apps often do not go in without complaints).
In fact, the SuSE update site often instructs the user to force packages.
When testing beta, it is just sometimes necessary. As for not reporting
problems to developers, thanks for the suggestion, but I'll let the
developers tell me that - which none have yet!
--- Zeljko Vukman <[EMAIL PROTECTED]> wrote:
> Yes, you're doing wrong. It will work every time, but God knows
> how many unresolved dependencies you get as a result of doing this.
> If you experience that your fresh installed apps don't work as they
> should
> don't send bug reports to developers.
>
> -----Oprindelig meddelelse-----
> Fra: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]På vegne af Ron Heron
> Sendt: 19. januar 2001 00:19
> Til: [EMAIL PROTECTED]
> Emne: Re: [expert] RPM Updates
>
>
> I may be doing it wrong, but by golly it has worked everytime!
>
> #rpm -Uhv --force --nodeps *rpm
>
> Ron
>
>
>
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
