jj/lib/gen-protos/Cargo.toml

[package]
name = "gen-protos"
description = "Generate Protocol Buffers definitions for the jj-lib crate"
publish = false

version.workspace = true
edition.workspace = true
license.workspace = true

[dependencies]
prost-build.workspace = true
lib: replace protobuf crate with prost 2022-12-21 19:14:46 +00:00			`[package]`
			`name = "gen-protos"`
cargo: unify a lot of crate metadata in the workspace Summary: There's no need to go around specifying `rust-version` or `edition` or `version` several times, now that we have a global workspace. Instead, inherit workspace metadata from the top-level Cargo.toml file. Signed-off-by: Austin Seipp <aseipp@pobox.com> Change-Id: Iaf905445978ed2b3377239dcdb8a6c32 2023-08-05 22:14:11 +00:00			`description = "Generate Protocol Buffers definitions for the jj-lib crate"`
lib: replace protobuf crate with prost 2022-12-21 19:14:46 +00:00			`publish = false`

cargo: unify a lot of crate metadata in the workspace Summary: There's no need to go around specifying `rust-version` or `edition` or `version` several times, now that we have a global workspace. Instead, inherit workspace metadata from the top-level Cargo.toml file. Signed-off-by: Austin Seipp <aseipp@pobox.com> Change-Id: Iaf905445978ed2b3377239dcdb8a6c32 2023-08-05 22:14:11 +00:00			`version.workspace = true`
			`edition.workspace = true`
			`license.workspace = true`

lib: replace protobuf crate with prost 2022-12-21 19:14:46 +00:00			`[dependencies]`
cargo: unify dependency versions through workspace deps Summary: This moves all dependencies across the jj-lib and jj-cli crates into the top-level Cargo file; with that, we can change each crate instead to just inherit the workspace version, with the toggled features enabled, by setting a dependency such as: dep.workspace = true in the relevant Cargo.toml file. This doesn't actually change any of the build semantics (from what I can tell) nor the lockfile, and seems to respond normally. There are more cleanups that can follow. Two notes: - Dependabot seems to work fine, based on what I've seen in other repos. - `cargo add` doesn't seem to know how to add packages to a top-level `workspace.dependencies` field; instead you can `cargo add -p jj-cli` and move the entries, at least. Signed-off-by: Austin Seipp <aseipp@pobox.com> Change-Id: I307827e5f15c0d8ea8e2a80ec793d3c7 2023-08-05 16:14:11 +00:00			`prost-build.workspace = true`