jj/lib/Cargo.toml

[package]
name = "jujutsu-lib"
version = "0.3.3"
authors = ["Martin von Zweigbergk <martinvonz@google.com>"]
edition = "2021"
license = "Apache-2.0"
description = "Library for Jujutsu (an experimental VCS)"
homepage = "https://github.com/martinvonz/jj"
repository = "https://github.com/martinvonz/jj"
documentation = "https://docs.rs/jujutsu"
readme = "../README.md"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[build-dependencies]
protobuf-codegen-pure = "2.27.1"
version_check = "0.9.4"

[dependencies]
backoff = "0.4.0"
blake2 = "0.10.4"
bytes = "1.1.0"
byteorder = "1.4.3"
chrono = "0.4.19"
config = "0.11.0"
dirs = "4.0.0"
git2 = "0.14.2"
hex = "0.4.3"
itertools = "0.10.3"
maplit = "1.0.2"
pest = "2.1.3"
pest_derive = "2.1.0"
protobuf = { version = "2.27.1", features = ["with-bytes"] }
rand = "0.8.4"
regex = "1.5.4"
serde_json = "1.0.78"
tempfile = "3.3.0"
thiserror = "1.0.30"
uuid = { version = "0.8.2", features = ["v4"] }
whoami = "1.2.1"
zstd = "0.10.0"

[dev-dependencies]
assert_matches = "1.5.0"
num_cpus = "1.13.1"
test-case = "1.2.3"

[features]
vendored-openssl = ["git2/vendored-openssl"]
import commit 0f15be02bf4012c116636913562691a0aaa7aed2 from my hg repo 2020-12-12 08:00:42 +00:00			`[package]`
project: rename project from Jujube to Jujutsu "Jujutsu" is probably much more familiar and relatable to most people. Also, I'm still not sure how "jujube" is supposed to be pronounced :P 2021-05-15 16:16:31 +00:00			`name = "jujutsu-lib"`
release: bump version to 0.3.3 (skipping 0.3.2) I forgot to bump the version to 0.3.2 before tagging and releasing it, so the released 0.3.2 has version number 0.3.1 in the source code and (therefore) reported from `jj --version`. I'm therefore bumping it from 0.3.1 to 0.3.3 now, so there can be a matching 0.3.3 release. 2022-03-16 19:05:39 +00:00			`version = "0.3.3"`
import commit 0f15be02bf4012c116636913562691a0aaa7aed2 from my hg repo 2020-12-12 08:00:42 +00:00			`authors = ["Martin von Zweigbergk <martinvonz@google.com>"]`
cargo: upgrade to Rust 2021 (just to stay up to date) 2021-12-14 05:38:10 +00:00			`edition = "2021"`
cargo: fill in crates.io metadata 2021-01-03 16:45:07 +00:00			`license = "Apache-2.0"`
project: rename project from Jujube to Jujutsu "Jujutsu" is probably much more familiar and relatable to most people. Also, I'm still not sure how "jujube" is supposed to be pronounced :P 2021-05-15 16:16:31 +00:00			`description = "Library for Jujutsu (an experimental VCS)"`
cargo: fill in crates.io metadata 2021-01-03 16:45:07 +00:00			`homepage = "https://github.com/martinvonz/jj"`
			`repository = "https://github.com/martinvonz/jj"`
project: rename project from Jujube to Jujutsu "Jujutsu" is probably much more familiar and relatable to most people. Also, I'm still not sure how "jujube" is supposed to be pronounced :P 2021-05-15 16:16:31 +00:00			`documentation = "https://docs.rs/jujutsu"`
cargo: fill in crates.io metadata 2021-01-03 16:45:07 +00:00			`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: upgrade dependencies 2022-02-10 06:19:16 +00:00			`protobuf-codegen-pure = "2.27.1"`
build: conditionally use `map_first_last` feature if available 2022-02-21 06:14:13 +00:00			`version_check = "0.9.4"`
import commit 0f15be02bf4012c116636913562691a0aaa7aed2 from my hg repo 2020-12-12 08:00:42 +00:00
			`[dependencies]`
cargo: upgrade backoff 2022-02-10 06:15:38 +00:00			`backoff = "0.4.0"`
cargo: bump blake2 from 0.10.2 to 0.10.4 Bumps [blake2](https://github.com/RustCrypto/hashes) from 0.10.2 to 0.10.4. - [Release notes](https://github.com/RustCrypto/hashes/releases) - [Commits](https://github.com/RustCrypto/hashes/commits) --- updated-dependencies: - dependency-name: blake2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> 2022-03-17 04:10:14 +00:00			`blake2 = "0.10.4"`
cargo: run `cargo upgrade` For no particular reason other than to stay up to date. 2021-11-30 17:14:21 +00:00			`bytes = "1.1.0"`
			`byteorder = "1.4.3"`
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"`
cargo: run `cargo upgrade` For no particular reason other than to stay up to date. 2021-11-30 17:14:21 +00:00			`config = "0.11.0"`
			`dirs = "4.0.0"`
cargo: use libgit2 with vendored OpenSSL (#73) I was able to build a working musl binary with this change, by running this command: ``` cargo build --release --target x86_64-unknown-linux-musl ``` Thanks to @arxanas for the tip. 2022-03-13 07:03:44 +00:00			`git2 = "0.14.2"`
cargo: run `cargo upgrade` For no particular reason other than to stay up to date. 2021-11-30 17:14:21 +00:00			`hex = "0.4.3"`
cargo: upgrade dependencies 2022-02-10 06:19:16 +00:00			`itertools = "0.10.3"`
tests: start using the maplit crate 2020-12-23 17:39:09 +00:00			`maplit = "1.0.2"`
revsets: define grammar in pest 2021-04-14 23:54:27 +00:00			`pest = "2.1.3"`
			`pest_derive = "2.1.0"`
cargo: upgrade dependencies 2022-02-10 06:19:16 +00:00			`protobuf = { version = "2.27.1", features = ["with-bytes"] }`
cargo: run `cargo upgrade` For no particular reason other than to stay up to date. 2021-11-30 17:14:21 +00:00			`rand = "0.8.4"`
gitignores: add own implementation and stop using libgit2's This is to address issue #8. I haven't added the optimization to avoid walking all the files in `target/` yet. Even so, this patch still speeds up `jj st` in this repo, with ~13k files in `target/`, from ~320 ms to ~100 ms (-5.1dB). The time actually checking if paths match gitignores seems to go down from 116 ms to 6 ms. I think that's mostly because libgit2 has to look for `.gitignore` files in every parent directory every time we ask it about a file, while the rewritten code looks for a `.gitignore` file only when visiting a new directory. 2021-05-12 16:43:58 +00:00			`regex = "1.5.4"`
cargo: upgrade dependencies 2022-02-10 06:19:16 +00:00			`serde_json = "1.0.78"`
			`tempfile = "3.3.0"`
cargo: run `cargo upgrade` For no particular reason other than to stay up to date. 2021-11-30 17:14:21 +00:00			`thiserror = "1.0.30"`
			`uuid = { version = "0.8.2", features = ["v4"] }`
			`whoami = "1.2.1"`
cargo: upgrade dependencies 2022-02-10 06:19:16 +00:00			`zstd = "0.10.0"`
import commit 0f15be02bf4012c116636913562691a0aaa7aed2 from my hg repo 2020-12-12 08:00:42 +00:00
			`[dev-dependencies]`
build: use `assert_matches` crate The `assert_matches` feature is nightly-only, so use this crate as a shim. 2022-02-21 05:45:09 +00:00			`assert_matches = "1.5.0"`
cargo: upgrade dependencies 2022-02-10 06:19:16 +00:00			`num_cpus = "1.13.1"`
			`test-case = "1.2.3"`
cargo: use libgit2 with vendored OpenSSL (#73) I was able to build a working musl binary with this change, by running this command: ``` cargo build --release --target x86_64-unknown-linux-musl ``` Thanks to @arxanas for the tip. 2022-03-13 07:03:44 +00:00
			`[features]`
			`vendored-openssl = ["git2/vendored-openssl"]`