chore: remove rustfmt check in configure
What the developer wrote
Authored by Lakshya Singh
chore: remove rustfmt check in configure
rustfmt isn’t needed for production builds and cargo is sufficient
[ Also, rustfmt --version exits with status 1 due to deprecation --RR ]
Changelog-None
What changed, and why it matters
This commit removes a check for the rustfmt tool during the build configuration step. It does not change any production code, network behavior, or security logic. The change is purely a build-system cleanup because rustfmt is not required for production builds and its version command now returns an error due to deprecation.
No security action needed. Reviewers may optionally verify that CI still enforces rustfmt where desired, since the production build no longer requires it.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The configure script’s default_rust_setting() previously required both cargo and rustfmt to be present to enable Rust support. The patch drops the rustfmt –version check, leaving only cargo –version. This avoids a deprecation-induced non-zero exit from rustfmt –version and reflects that rustfmt is a formatting tool, not a build dependency.
Changed components
configure scriptbuild systemInspect captured patch +1 / −1
diff --git a/configure b/configure
index eb135239..f0cc855b 100755
--- a/configure
+++ b/configure
@@ -152,7 +152,7 @@ default_valgrind_setting()
default_rust_setting()
{
- if cargo --version > /dev/null 2>&1 && rustfmt --version >/dev/null 2>&1; then
+ if cargo --version > /dev/null 2>&1; then
echo 1
else
echo 0
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.