I would like to suggest something for a RPM installer feature,
make it so instead of only telling you that its missing
libmxo25.so.9 or some dumb thing like that,
have it also tell you what rpm that this file is found in,
or give at least some possibilities of software packages
or names of softwares that it could be found in so
we don't have to go pestering every linux list
on the planet asking where wehre where werhe. screw the spelling
On Thu, 25 May 2000, Dan Jones wrote:
> I have had similar experiences, and think the problem has to do with the
> way that the RPMs (and the RPM database) specify dependencies. It
> appears to me that when an RPM is installed, an entry is made in the
> database of what files have been installed (e.g.
> "/usr/lib/libexample.so.1") When another RPM checks for dependencies,
> it checks that database (e.g. for "libexample.so.1".
>
> Alas, as far as the database is concerned, "/usr/lib/libexample.so.1" is
> *different* that "libexample.so.1".
>
> A similar problem can occur when one of your dependencies was installed
> from a tar file (or anything that isn't an RPM). In this case no entry
> at all occurs in the RPM database.
>
> IF you really have the necessary files/packages installed, just use
> --nodeps when you install using RPM.
