Cargo update

Cargo.toml

@@ -3,9 +3,17 @@ name = "chainerror"
 version = "0.1.0"
 authors = ["Harald Hoyer <harald@redhat.com>"]
 edition = "2018"
+license = "MIT"
+documentation = "https://docs.rs/chainerror"
+homepage = "https://haraldh.github.io/chainerror/"
+repository = "https://github.com/haraldh/chainerror"
+description = "Yet another error boilerplate library."
+keywords = ["error"]
+categories = ["rust-patterns"]
+readme = "README.md"
 
 [features]
 default = [ ]
 no-fileline = []
 display-cause = []
-no-debug-cause = []
+no-debug-cause = []

README.md

@@ -3,6 +3,8 @@
 `chainerror` provides an error backtrace like `failure` without doing a real backtrace, so even after you `strip` your
 binaries, you still have the error backtrace.
 
+`chainerror` has no depenendencies!
+
 `chainerror` uses `.source()` of `std::error::Error` along with `line()!` and `file()!` to provide a nice debug error backtrace.
 It encapsulates all types, which have `Display + Debug` and can store the error cause internally.