[PATCH] doc: Update guidance about Rust package nameing.

DoneSubmitted by Hartmut Goebel.
Details
One participant
  • Hartmut Goebel
Owner
unassigned
Severity
normal
H
H
Hartmut Goebel wrote on 11 Jan 15:33 +0100
(address . guix-patches@gnu.org)
592a793b592606d3e96ab789ddee607827641872.1610375602.git.h.goebel@crazy-compilers.com
* doc/contributing.texi (Rust Crates): Explain versions suffix based on packages version and Crate "caret" versioning.--- doc/contributing.texi | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
Toggle diff (21 lines)diff --git a/doc/contributing.texi b/doc/contributing.texiindex d0ab08336a..b76f118369 100644--- a/doc/contributing.texi+++ b/doc/contributing.texi@@ -802,10 +802,10 @@ To prevent namespace collisions we prefix all other Rust packages with the dashes should remain in place. In the rust ecosystem it is common for multiple incompatible versions of a-package to be used at any given time, so all packages should have a versioned-suffix. If a package has passed version 1.0.0 then just the major version-number is sufficient (e.g.@: @code{rust-clap-2}), otherwise the version suffix-should contain both the major and minor version (e.g.@: @code{rust-rand-0.6}).+package to be used at any given time, so all package definitions should have a+versioned suffix. The versioned suffix is the left-most non-zero digit (and+any leading zeros, of course). This follows the ``caret'' version scheme+intended by Cargo. Examples@: @code{rust-clap-2}, @code{rust-rand-0.6}. Because of the difficulty in reusing rust packages as pre-compiled inputs for other packages the Cargo build system (@pxref{Build Systems,-- 2.21.3
H
H
Hartmut Goebel wrote on 29 Jan 22:52 +0100
Re: bug#45783: Acknowledgement ([PATCH] doc: Update guidance about Rust package nameing.)
(address . 45783-close@debbugs.gnu.org)
84a70fc5-bfac-f533-f029-03bd6d440bb8@crazy-compilers.com
pushed as 784048c27b90e32814f6d06363f94fb3f9bf0a6d
?