From: Hartmut Goebel <h.goebel@goebel-consult.de>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>,
Maxime Devos <maximedevos@telenet.be>,
guix-devel@gnu.org
Subject: Re: (rust) Do we always need to package minor versions separately?
Date: Thu, 10 Mar 2022 12:40:24 +0100 [thread overview]
Message-ID: <5d054839-d2ad-4d0a-d6da-bcc17199b51b@goebel-consult.de> (raw)
In-Reply-To: <c1e8572c9196fbb4d2638747d29a7f596505642f.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
Am 08.03.22 um 22:01 schrieb Liliana Marie Prikler:
> In practice, we assume 0.y.z be compatible with 0.y.a, a < z or the
> other way round depending on which direction you're looking at. I'm
> not sure if this is a rust fortification of semver
This is backed by the cargo manual
<https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html>:
An update is allowed if the new version number *does not modify the
left-most non-zero digit* in the major, minor, patch grouping.
--
Schönen Gruß
Hartmut Goebel
Dipl.-Informatiker (univ), CISSP, CSSLP, ISO 27001 Lead Implementer
Information Security Management, Security Governance, Secure Software
Development
Goebel Consult, Landshut
http://www.goebel-consult.de
Blog:
https://www.goe-con.de/blog/nicht-pgp-ist-gescheitert-die-entwickler-haben-versagt
Kolumne:
https://www.goe-con.de/hartmut-goebel/cissp-gefluester/2012-02-bring-your-own-life-glosse
[-- Attachment #2: Type: text/html, Size: 2377 bytes --]
prev parent reply other threads:[~2022-03-10 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 17:43 (rust) Do we always need to package minor versions separately? Maxime Devos
2022-03-08 21:01 ` Liliana Marie Prikler
2022-03-10 11:40 ` Hartmut Goebel [this message]
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=5d054839-d2ad-4d0a-d6da-bcc17199b51b@goebel-consult.de \
--to=h.goebel@goebel-consult.de \
--cc=guix-devel@gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=maximedevos@telenet.be \
/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.