The LevelDB package uses the upstream google implementation, while we depend on the niceities of the basho fork (google's version is used in chrome for things like bookmarks, basho's version is used as a backend for their riak software and scales much better with a large number of DBs). leveldb and its -devel package should be removed as requires.
Additionally, the Requires: field shouldn't require much of anything. RPM will sort out what shared libraries are needed, which shouldn't be much since we link the binaries statically:
ldd ibp_server
linux-vdso.so.1 => (0x00007ffcdbbfb000)
libdb-4.7.so => /lib64/libdb-4.7.so (0x0000003c68200000)
librt.so.1 => /lib64/librt.so.1 (0x0000003c60200000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003c5f200000)
libdl.so.2 => /lib64/libdl.so.2 (0x0000003c5f600000)
libm.so.6 => /lib64/libm.so.6 (0x0000003c5fa00000)
libz.so.1 => /lib64/libz.so.1 (0x0000003c5fe00000)
libc.so.6 => /lib64/libc.so.6 (0x0000003c5ee00000)
/lib64/ld-linux-x86-64.so.2 (0x0000003c5ea00000)
The
LevelDBpackage uses the upstream google implementation, while we depend on the niceities of the basho fork (google's version is used in chrome for things like bookmarks, basho's version is used as a backend for their riak software and scales much better with a large number of DBs). leveldb and its -devel package should be removed as requires.Additionally, the Requires: field shouldn't require much of anything. RPM will sort out what shared libraries are needed, which shouldn't be much since we link the binaries statically: