Description of problem: The .so and .a should be in a -devel package. Or maybe not shipped at all since there is no header. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
It looks like some of the scrollkeeper utilities dynamically link to libscrollkeeper.so.0. $ ldd /usr/bin/scrollkeeper* | grep scrollkeeper Does that not mean the .so needs to be packaged with the binaries? I agree that I don't see much point in shipping libscrollkeeper.a.
Indeed, but not against the /usr/lib/libscrollkeeper.so link. It is only needed at build time, so should be in -devel. If all that links against libscrollkeeper is in the scrollkeeper source package then the .so is no needed for them. And the lack of headers certainly shows that it is not meant to be linked against by programs outside of the scrollkeeper package itself.
Ah, I see. Indeed there seems to be no packages requiring the .so or .a. $ repoquery --whatrequires libscrollkeeper.a $ repoquery --whatrequires libscrollkeeper.so $ repoquery --whatrequires libscrollkeeper.so.0 scrollkeeper-0:0.3.14-8.fc6.i386 So a -devel package does not make sense. I think I'd prefer to just not ship those files. Changing the summary appropriately.
Fixed in scrollkeeper-0.3.14-9.fc7.