There is no way a rpm2html configure time to know the library needed
for the link. See bug #79654 for an easy way to solve this in a completely
generic fashion.

Sophistry.

What, you need a script to tell you *NOT* to link
against -loracle and every other library in the world?

Linking against -ldb3.1 from a compat package
is broken no matter what.

Linking against any Berkeley DB library in 7.2
and beyond is unnecssary.

Why don't you add /usr/bin/rpm-config to rpm2html
and just fix your package?

Trivially this can't be done in rpm2html because the options are known only
by rpm configure script in a reliable fashion.
You're suggesting I do guess work to make my application link against your
library while the inforamtion needed is availble in an AUTOMATED way within
rpm configure. All library having minimal respect for the application builder
provide this kind of informations as well as a way to get the version of the
library. It's trivial for you to do it in an exact way. It's pure guess work
and hell to maintain in each and every application trying to use it. This is
so commonsense this should NOT have to be said, really !!!

Daniel

Removed the test for db-3.1, applied old 7.3 patch, this is a fix with will
work only on that version of Red Hat Linux. Should land in Rawhide soon.