proxmox/proxmox-subscription/Cargo.toml

34 lines
1.0 KiB
TOML
Raw Normal View History

[package]
name = "proxmox-subscription"
description = "Proxmox subscription utilitites"
version = "0.5.0"
authors.workspace = true
edition.workspace = true
exclude.workspace = true
homepage.workspace = true
license.workspace = true
repository.workspace = true
rust-version.workspace = true
[dependencies]
anyhow.workspace = true
base64 = { workspace = true, optional = true }
hex = { workspace = true, optional = true }
openssl = { workspace = true, optional = true }
regex.workspace = true
serde.workspace = true
serde_json.workspace = true
proxmox-http = { workspace = true, optional = true, features = ["client-trait", "http-helpers"] }
proxmox-serde.workspace = true
proxmox-sys = { workspace = true, optional = true }
proxmox-time = { workspace = true, optional = true }
proxmox-schema = { workspace = true, features = ["api-macro"], optional = true }
[features]
default = ["impl"]
impl = [ "dep:base64", "dep:hex", "dep:openssl", "dep:proxmox-http", "dep:proxmox-sys", "dep:proxmox-time"]
build: use weak and namespaced features to reduce the creep of optional dependencies being exposed as features. this requires cargo 0.63 (and debcargo built against at least that version), but greatly reduces the number of binary packages and provides generated, while still allowing sensible selection of optional dependencies via the explicit feature meant for pulling them in. diff stat for running `make deb` after this change: proxmox-http/debian/control | 226 ++++-------------------------------- proxmox-router/debian/control | 74 +----------- proxmox-schema/debian/control | 53 ++------- proxmox-subscription/debian/control | 17 +-- proxmox-sys/debian/control | 51 +++----- proxmox-tfa/debian/control | 110 ++---------------- 6 files changed, 72 insertions(+), 459 deletions(-) the 'dep:' prefix marks something on the RHS inside the features section as dependency, it's only allowed if the string after it is an optional dependency an no explicit feature of the same name exists. if all pointers to the optional dependency in the features section are marked as such, the optional dependency itself will not be exposed as a feature (either on the cargo or debian/control level). the '?' suffix marks dependencies as "weak", which only enables the optional dependency + its feature(s) if the optional dependency itself is also enabled. it has no effect on d/control since such a relationship is not encodable in Debian package relations, but it does affect cargo dependency resolution and allows skipping the build of unneeded optional dependencies in some cases. with no packages/crates depending on the no longer exposed automatically generated features/packages, so these are safe to remove even though it's technically a breaking change. Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
2022-08-22 12:24:04 +03:00
api-types = ["dep:proxmox-schema"]