ok/jj
1
0
Fork 0
forked from mirrors/jj
Code Pull requests Activity
jj/lib/Cargo.toml

41 lines
977 B
TOML
Raw Normal View History

import commit 0f15be02bf4012c116636913562691a0aaa7aed2 from my hg repo
2020-12-12 08:00:42 +00:00
[package]
cargo: rename crates to names available on crates.io I'm preparing to publish an early version before someone takes the name(s) on crates.io. "jj" has been taken by a seemingly useless project, but "jujube" and "jujube-lib" are still available, so let's use those.
2021-01-03 16:45:07 +00:00
name = "jujube-lib"
cargo: release 0.1.1 This release is mostly to fix the regressed binary name (back from `jujube` to `jj`).
2021-01-04 06:55:16 +00:00
version = "0.1.1"
import commit 0f15be02bf4012c116636913562691a0aaa7aed2 from my hg repo
2020-12-12 08:00:42 +00:00
authors = ["Martin von Zweigbergk <martinvonz@google.com>"]
edition = "2018"
cargo: fill in crates.io metadata
2021-01-03 16:45:07 +00:00
license = "Apache-2.0"
description = "Library for Jujube (an experimental VCS)"
homepage = "https://github.com/martinvonz/jj"
repository = "https://github.com/martinvonz/jj"
documentation = "https://docs.rs/jujube"
readme = "../README.md"
import commit 0f15be02bf4012c116636913562691a0aaa7aed2 from my hg repo
2020-12-12 08:00:42 +00:00
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
protobuf: generate code at build-time I had tried to generate the protobuf code at build time many months ago, but decided against it because it slowed down the build too much. I didn't realize there was the "cargo:rerun-if-changed=<filename>" feature that time. Given that that exists, it seems like an obvious win to generate the source code at build time. I put the generated sources in `$OUT_DIR` (where [1] says they should be), then include them in the `protos` module by using the `include!` macro. The biggest problem with that is that I couldn't get IntelliJ to understand it, even after enabling the experimental features described in [2]. [1] https://doc.rust-lang.org/cargo/reference/build-script-examples.html#code-generation [2] https://github.com/intellij-rust/intellij-rust/issues/1908#issuecomment-592773865
2020-12-24 07:12:18 +00:00
[build-dependencies]
cargo: update dependencies For no reason other than to stay up to date.
2020-12-24 04:55:12 +00:00
protobuf-codegen-pure = "2.18.1"
import commit 0f15be02bf4012c116636913562691a0aaa7aed2 from my hg repo
2020-12-12 08:00:42 +00:00
[dependencies]
git_store: use exponential backoff when retrying note-writing I have never run into this being a problem in practice, but this change is a stepping stone for two things: 1. Using exponential backoff for other locks (in particular the working copy). 2. Making the Git store write a ref for conflict objects, so they don't get GC'd (I want to do that before even I start dogfooding).
2020-12-25 06:56:05 +00:00
backoff = "0.2.1"
cargo: update blake2 For no reason other than to stay up to date.
2020-12-24 09:15:38 +00:00
blake2 = "0.9.1"
cargo: update dependencies For no reason other than to stay up to date.
2020-12-24 04:55:12 +00:00
bytes = "1.0.0"
import commit 0f15be02bf4012c116636913562691a0aaa7aed2 from my hg repo
2020-12-12 08:00:42 +00:00
byteorder = "1.3.4"
cargo: update dependencies For no reason other than to stay up to date.
2020-12-24 04:55:12 +00:00
chrono = "0.4.19"
config = "0.10.1"
diff = "0.1.12"
dirs = "3.0.1"
git2 = "0.13.14"
hex = "0.4.2"
tests: start using the maplit crate
2020-12-23 17:39:09 +00:00
maplit = "1.0.2"
cargo: update dependencies For no reason other than to stay up to date.
2020-12-24 04:55:12 +00:00
protobuf = { version = "2.18.1", features = ["with-bytes"] }
rand = "0.8.0"
serde_json = "1.0.60"
tempfile = "3.1.0"
thiserror = "1.0.22"
uuid = { version = "0.8.1", features = ["v4"] }
whoami = "1.0.1"
zstd = "0.6.0"
import commit 0f15be02bf4012c116636913562691a0aaa7aed2 from my hg repo
2020-12-12 08:00:42 +00:00
[dev-dependencies]
test-case = "1.0.0"
Copy permalink