chore: bump weedb version

Cargo.toml

@@ -86,7 +86,7 @@ tracing-subscriber = { version = "0.3", features = ["env-filter"] }
 tracing-test = "0.2"
 trait-variant = "0.1.2"
 triomphe = "0.1.11"
-weedb = "0.1.1"
+weedb = "0.2.2"
 x509-parser = "0.15"
 
 # local deps

README.md

@@ -1,16 +1,14 @@
 # tycho
 
-# Pre-requisites
+## Pre-requisites
 
 - [rust](https://rustup.rs/)
 - [just](https://pkgs.org/download/just)
 - [zstd](https://pkgs.org/download/zstd)
 - [clang](https://pkgs.org/download/clang)
 - [llvm](https://pkgs.org/download/llvm)
-- [fzf](https://github.com/junegunn/fzf?tab=readme-ov-file#using-linux-package-managers)
-  for just help menu
 
-# testing
+## Testing
 
 To run tests from ci:
 
@@ -22,4 +20,32 @@ To interactivly choose what to run:
 
 ```bash
 just
-```
+```
+
+## Prebuilt RocksDB
+
+By default, we compile RocksDB (a C++ project) from source during the build.
+By linking to a prebuilt copy of RocksDB this work can be avoided
+entirely. This is a huge win, especially if you clean the `./target` directory
+frequently.
+
+To use a prebuilt RocksDB, set the `ROCKSDB_LIB_DIR` environment variable to
+a location containing `librocksdb.a`:
+
+```bash
+export ROCKSDB_LIB_DIR=/usr/lib/
+cargo build -p tycho-cli
+```
+
+Note, that the system must provide a recent version of the library which,
+depending on which operating system you're using, may require installing packages
+from a testing branch. Or you could build the RocksDB from source manually:
+
+```bash
+cd /path/to
+git clone https://github.com/facebook/rocksdb.git
+cd rocksdb
+git checkout v8.10.0
+make -j 10 static_lib
+export ROCKSDB_LIB_DIR=/path/to/rocksdb
+```