1) tools/db_tool.c from @rpm5.org includes all tool functionality,
but requires only a single "partial static link" thereby removing
much of the bloat.
2) use alternatives to easily flip between versioned executables.
Specifically, burying the version into the tool names like
/usr/bin/dbXY_*
is stoopidness. Better would be a version specific .../bin
directory, and use alternatives to switch executables in/out.
The -I/usr/include/dbXY convention is mostly okay (having
a single /usr/include/db alternative link is just asking for
bug reports), but any of the usual hinting with db-config/libdbXY.pc/libdb-X.Y.la
likely helps targeting multiply installed versions of Berkeley DB while developing.
Extra credit useful enhancements:
1) tools/db_tool.c from @rpm5.org includes all tool functionality,
but requires only a single "partial static link" thereby removing
much of the bloat.
2) use alternatives to easily flip between versioned executables.
Specifically, burying the version into the tool names like libdbXY. pc/libdb- X.Y.la
/usr/bin/dbXY_*
is stoopidness. Better would be a version specific .../bin
directory, and use alternatives to switch executables in/out.
The -I/usr/include/dbXY convention is mostly okay (having
a single /usr/include/db alternative link is just asking for
bug reports), but any of the usual hinting with db-config/
likely helps targeting multiply installed versions of Berkeley DB while developing.