branch master updated: doc: Update guidance about Rust package naming.

[guix-commits]

This is an automated email from the git hooks/post-receive script.

htgoebel pushed a commit to branch master
in repository guix.

The following commit(s) were added to refs/heads/master by this push:
     new 784048c  doc: Update guidance about Rust package naming.
784048c is described below

commit 784048c27b90e32814f6d06363f94fb3f9bf0a6d
Author: Hartmut Goebel <h.goebel@crazy-compilers.com>
AuthorDate: Thu Apr 30 22:53:47 2020 +0200

    doc: Update guidance about Rust package naming.
    
    * 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(-)

diff --git a/doc/contributing.texi b/doc/contributing.texi
index d1619d3..f167df0 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,