docs: document naming convention for Rust subprojects

Place the convention so that distro packagers know that they can
rely on it, and not following it is a bug.

This is the same convention that Meson uses for Cargo subprojects,
but Mesa is not using them as they are experimental and not really
usable yet.

Acked-by: Faith Ekstrand <faith.ekstrand@collabora.com>
Reviewed-by: Gurchetan Singh <gurchetansingh@chromium.org>
Tested-by: Gurchetan Singh <gurchetansingh@chromium.org>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/36284>
This commit is contained in:
Paolo Bonzini 2025-07-22 10:41:59 +02:00 committed by Marge Bot
parent 8ea232a9ae
commit 2e4a8e98bd

View file

@ -1,6 +1,14 @@
Rust
====
Rust Subproject Names
---------------------
All Rust subprojects should follow the convention ``NAME-SEMVER-rs``,
where ``SEMVER`` is the version up to and including the first nonzero
component. For example, ``zerocopy-0.8.13`` becomes ``zerocopy-0.8-rs``,
whereas ``syn-2.0.66`` becomes ``syn-2-rs``.
Rust Update Policy
------------------