Thanks - that was what I was afraid of.
It's true if you start out with Redhat and do an all-rpm install, it works
fine and is quite slick. But what about if you installed Linux without rpm
and installed rpm later (after all your libs, etc. are already installed)?
This is one of my cases - the other is more minor and I guess I can get the
rpms of the libs I've installed from tarballs and do a --justdb.
> ----------
> From: Tony Nugent[SMTP:[EMAIL PROTECTED]]
> Sent: Monday, August 16, 1999 6:28 PM
> To: Sumpter, Lloyd
> Cc: Linux Applications Email List
> Subject: Re: Updating RPM database
>
> On Mon Aug 16 1999 at 09:58, "Sumpter, Lloyd" wrote:
>
> > Is there a "fast" way to update the rpm database, perhaps using
> > ldconfig to show it what libraries are actually available? (I don't
> > care if utilities, apps, etc. aren't there - I'm just concerned with
> > libs)
>
> No.
>
> Best way out of this to get it done "cleanly" is to create an rpm file
> that has the libraries in it, then install this. Messy, it works, and
> it means that you don't have to do "rpm -ih --nodeps" on a package
> that you know does have available the libraries etc it needs somewhere
> on your system (preferably in /usr/local).
>
> I haven't hit this problem in ages (and I work with linux and redhat
> installations every day in my job)... I've *always* managed to find
> packages that provide the dependencies for applications that I've
> wanted to install.
>
> Cheers
> Tony
> -=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-
> Tony Nugent <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
> Computer Systems Officer Faculty of Science
> University of Southern Queensland, Toowoomba Oueensland Australia
> -=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-
>
