Automatic RPM provides for libraries
Ralf Ertzinger
fedora at camperquake.de
Sat Nov 10 15:13:08 UTC 2007
Hi.
I just notices something strange on my local system and would
like to check if I screwed up or something in RPM changed.
Assume I package a library and the RPM file contains two files:
/usr/lib/libfoo.so.1 -> libfoo.so.1.0.0
/usr/lib/libfoo.so.1.0.0
Now, my experience so far was that the RPM file will (automagically)
Provide: libfoo.so.1
Now, several RPMs I built locally instead
Provide: libfoo.so.1.0.0
This kind of wreaks havoc with installed programs which depend on
the old requires.
Did I screw up?
Has RPM changed?
Has something in libfoo changed that causes this?
More information about the fedora-devel-list
mailing list