v0.2. Remove backtrace from default dependency set.

without.crypto
Richard Newman 6 years ago
parent 5169696d0c
commit a07fb4e452
  1. 14
      Cargo.toml
  2. 5
      README.md

@ -1,21 +1,31 @@
[package]
name = "rkv"
version = "0.1.0"
version = "0.2.0"
authors = ["Richard Newman <rnewman@twinql.com>"]
description = "A humane key-value store built on LMDB."
license = "Apache-2.0"
homepage = "https://github.com/mozilla-prototypes/rkv"
repository = "https://github.com/mozilla-prototypes/rkv"
[features]
default = []
backtrace = ["failure/backtrace", "failure/std"]
[dependencies]
arrayref = "0.3"
bincode = "0.9"
failure = "0.1"
lmdb = "0.7"
ordered-float = "0.5"
uuid = "0.5"
serde = "1.0"
# Get rid of failure's dependency on backtrace. Eventually
# backtrace will move into Rust core, but we don't need it here.
[dependencies.failure]
version = "0.1"
default_features = false
features = ["derive"]
[dev-dependencies]
tempdir = "0.3"

@ -13,3 +13,8 @@ It aims to achieve the following:
- Correctly restrict to one handle per process via a 'manager'.
- Use Rust's type system to make single-typed key stores (including LMDB's own integer-keyed stores) safe and ergonomic.
- Encode and decode values via `bincode`/`serde` and type tags, achieving platform-independent storage and input/output flexibility.
## Feature choices
If you specify the `backtrace` feature, backtraces will be enabled in `failure`
errors. This feature is disabled by default.

Loading…
Cancel
Save