From 8770e1062eaf2f72b29766954df4d14245f80151 Mon Sep 17 00:00:00 2001 From: Olivier 'reivilibre Date: Fri, 5 Jun 2026 15:57:57 +0100 Subject: [PATCH 1/3] Tweak wording of Rust crate dependency policy --- docs/deprecation_policy.md | 21 +++++++++++++-------- 1 file changed, 13 insertions(+), 8 deletions(-) diff --git a/docs/deprecation_policy.md b/docs/deprecation_policy.md index 06c724d3489..90ce2e655d0 100644 --- a/docs/deprecation_policy.md +++ b/docs/deprecation_policy.md @@ -79,11 +79,16 @@ concerned about the criteria for selecting minimum versions. The only thing of c is making sure we're not making it unnecessarily difficult for downstream package maintainers. Generally, this just means avoiding the bleeding edge for a few months. -The situation for Rust dependencies is fundamentally different. For packagers, the -concerns around Python dependency versions do not apply. The `cargo` tool handles -downloading and building all libraries to satisfy dependencies, and these libraries are -statically linked into the final binary. This means that from a packager's perspective, -the Rust dependency versions are an internal build detail, not a runtime dependency to -be managed on the target system. Consequently, we have even greater flexibility to -upgrade Rust dependencies as needed for the project. Some distros (e.g. Fedora) do -package Rust libraries, but this appears to be the outlier rather than the norm. +The situation for Rust dependencies is typically different and +the concerns around Python dependency versions typically do not apply. +For example, for packagers of Debian, the packagers have the choice of either +using a crate packaged in the distro, or vendoring crates in the source package for the application. + +This freedom to vendor a dependency crate for a specific application consequently gives us even greater flexibility to +upgrade Rust dependencies as needed for the project. + +(This is in contrast with Python dependencies, which are generally +installed system-wide by mainstream distributions' official packages.) + +Some distros (e.g. Fedora) do not vendor Rust dependencies in their +official application packages, but these cases appear to be less common. From a8634f4c7e431998d7578a547fc749d586951e70 Mon Sep 17 00:00:00 2001 From: Olivier 'reivilibre Date: Fri, 5 Jun 2026 16:05:29 +0100 Subject: [PATCH 2/3] Newsfile Signed-off-by: Olivier 'reivilibre --- changelog.d/19829.doc | 1 + 1 file changed, 1 insertion(+) create mode 100644 changelog.d/19829.doc diff --git a/changelog.d/19829.doc b/changelog.d/19829.doc new file mode 100644 index 00000000000..44dbc0eff43 --- /dev/null +++ b/changelog.d/19829.doc @@ -0,0 +1 @@ +Tweak wording of Rust crate dependency update policy. \ No newline at end of file From 0eb5b9d944805fd7686069d504574227a0e46157 Mon Sep 17 00:00:00 2001 From: Olivier 'reivilibre Date: Tue, 23 Jun 2026 15:27:57 +0100 Subject: [PATCH 3/3] wordwrap --- docs/deprecation_policy.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/deprecation_policy.md b/docs/deprecation_policy.md index 90ce2e655d0..7c537cbca8e 100644 --- a/docs/deprecation_policy.md +++ b/docs/deprecation_policy.md @@ -82,10 +82,11 @@ maintainers. Generally, this just means avoiding the bleeding edge for a few mon The situation for Rust dependencies is typically different and the concerns around Python dependency versions typically do not apply. For example, for packagers of Debian, the packagers have the choice of either -using a crate packaged in the distro, or vendoring crates in the source package for the application. +using a crate packaged in the distro, or vendoring crates in the source package for the +application. -This freedom to vendor a dependency crate for a specific application consequently gives us even greater flexibility to -upgrade Rust dependencies as needed for the project. +This freedom to vendor a dependency crate for a specific application consequently gives +us even greater flexibility to upgrade Rust dependencies as needed for the project. (This is in contrast with Python dependencies, which are generally installed system-wide by mainstream distributions' official packages.)