From: Hartmut Goebel <h.goebel@crazy-compilers.com> To: 45783@debbugs.gnu.org Subject: [bug#45783] [PATCH] doc: Update guidance about Rust package nameing. Date: Mon, 11 Jan 2021 15:33:49 +0100 Message-ID: <592a793b592606d3e96ab789ddee607827641872.1610375602.git.h.goebel@crazy-compilers.com> (raw) * 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 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
next reply other threads:[~2021-01-11 14:35 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-11 14:33 Hartmut Goebel [this message] [not found] ` <handler.45783.B.161037564313337.ack@debbugs.gnu.org> 2021-01-29 21:52 ` bug#45783: Acknowledgement ([PATCH] doc: Update guidance about Rust package nameing.) Hartmut Goebel
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://guix.gnu.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=592a793b592606d3e96ab789ddee607827641872.1610375602.git.h.goebel@crazy-compilers.com \ --to=h.goebel@crazy-compilers.com \ --cc=45783@debbugs.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
unofficial mirror of guix-patches@gnu.org This inbox may be cloned and mirrored by anyone: git clone --mirror https://yhetil.org/guix-patches/1 guix-patches/git/1.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 guix-patches guix-patches/ https://yhetil.org/guix-patches \ guix-patches@gnu.org public-inbox-index guix-patches Example config snippet for mirrors. Newsgroup available over NNTP: nntp://news.yhetil.org/yhetil.gnu.guix.patches AGPL code for this site: git clone http://ou63pmih66umazou.onion/public-inbox.git