Hi, I'm trying to figure out how RPM determines what files are provided by a package. I'm in a position where I need to upgrade a particular package that provides a couple of shared libraries. The new version provides newer versions of the libraries, and I want to add a couple of symlinks in the package that will act as the old versions of the libraries for backwards compatibility with all my other existing packages. Unfortunately, when I try to install the package, RPM spits out a huge list of dependencies that will be broken, and I can't figure out how to get the package to say that it actually does provide the libraries in question. I need to be able to overcome this problem instead of just using "--nodeps" because I'll be using autorpm to do a wide-scale deployment. Any feedback anyone has would be very welcome. TIA, Tom _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
