unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: help-guix@gnu.org
Subject: Re: Packaging a rust program with a lot of crates
Date: Sun, 23 Jul 2023 14:46:31 +0200	[thread overview]
Message-ID: <63db4221-1b21-f9fb-f121-c3df6f211fe3@crazy-compilers.com> (raw)
In-Reply-To: <ZLK3A3oge3-kyEbZ@Amsterdam>

Am 15.07.23 um 17:10 schrieb Paul Collignan:
> It is a little bit different for Rust packages, as described in the documentation:
> "In the rust ecosystem it is common for multiple incompatible versions of a 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"
> If I understand this correctly, one should keep all packages from 0.1 to 0.46 (for example, if the versions are numbered like this). But from 1.1 to 1.46 you only keep the last one.

This is correct. Anyhow, please keep in mind that the variable name for 
the 1.x package will stay "some-crate-1".

This follows the idea of semantic versioning, which rust follows.

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |



  parent reply	other threads:[~2023-07-23 12:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12 14:24 Packaging a rust program with a lot of crates Paul Collignan
2023-07-15 14:06 ` Wojtek Kosior via
2023-07-15 15:10   ` Paul Collignan
2023-07-15 16:16     ` Wojtek Kosior via
2023-07-23 12:46     ` Hartmut Goebel [this message]
2023-07-17 16:05   ` wolf

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=63db4221-1b21-f9fb-f121-c3df6f211fe3@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=help-guix@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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).