all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: guix-devel@gnu.org
Subject: (rust) Do we always need to package minor versions separately?
Date: Tue, 08 Mar 2022 18:43:22 +0100	[thread overview]
Message-ID: <7ac0e514d4f955b6983813c44387f9a0c38e138b.camel@telenet.be> (raw)

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

Hi guix,

Many rust crates are available in multiple versions in Guix
(say, rust-wayland-scanner-0.29).  The reason is that ((guix)Rust
Crates):

   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 (and any leading zeros, of course).  This follows the
“caret” version scheme intended by Cargo.  Examples ‘rust-clap-2’,
‘rust-rand-0.6’.

I understand the point about version incompatibilities in the land of
oxides.  However, what if a crate is being nice by striving to be
backwards-compatible, perhaps even using, say, semver, to indicate
incompatibilities clearly?  Is it then still necessary to package the
different minor versions, or would major versions suffice?

I would hope the latter, but I don't know any rust.

(Asked in the context of reviewing Rust patches like 54299 and perhaps
simplifying Rust packages in Guix.)

Greetings,
Maxime

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

             reply	other threads:[~2022-03-08 18:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 17:43 Maxime Devos [this message]
2022-03-08 21:01 ` (rust) Do we always need to package minor versions separately? Liliana Marie Prikler
2022-03-10 11:40   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7ac0e514d4f955b6983813c44387f9a0c38e138b.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=guix-devel@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.