From: Maxime Devos <maximedevos@telenet.be>
To: Evgenii Lepikhin <e.lepikhin@corp.mail.ru>
Cc: 54644@debbugs.gnu.org, Efraim Flashner <efraim@flashner.co.il>
Subject: [bug#54644] [PATCH 4/7] gnu: rust-minimal-lexical 0.2: Update to 0.2.1.
Date: Fri, 01 Apr 2022 08:38:23 +0200 [thread overview]
Message-ID: <1869e46d2f4e4081ec985d1c48d1bf702ecf38e5.camel@telenet.be> (raw)
In-Reply-To: <8735ixkb6a.fsf@corp.mail.ru>
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
Evgenii Lepikhin schreef op vr 01-04-2022 om 01:30 [+0300]:
> nom-7.0 is not forward compatible with nom-7.1. I need 7.1 for future
> contributions and this is why I added it into patchset.
Related: to reduce duplication, you can do
(define-public rust-nom-7.1
(package
(inherit rust-nom-7)
[...]))
that way, you can ‘copy’ the synopsis of rust-nom-7 without writing it
down again.
Also, if semver is used here, nom-7.0 is compatible with nom-7.1 (not
sure about the terminology here -- forwards? backwards?, but updating
it shouldn't cause any problems if semver is followed correctlu).
> In developer's manifest of nom-7.1 dependency on rust-minimal-lexical
> has been updated from 0.1 to 0.2. For both versions dependencies on
> exact versions on rust-minimal-lexical are pinned by crate developers
> and we cannot change it at will
We can do that, with some 'substitute*'. It is not guaranteed that it
will actually build, but there's a good chance that it will. Or that
it fails. Hard to say in advance. See, e.g., rust-version-sync@0.8.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-04-01 6:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 21:21 [bug#54644] [PATCH 1/7] gnu: rust-nom-locate-4: Add 4.0.0 Evgenii Lepikhin via Guix-patches via
2022-03-30 21:33 ` [bug#54644] [PATCH 2/7] gnu: rust-pretty 0.11: Update to 0.11.2 Evgenii Lepikhin via Guix-patches via
2022-03-30 21:35 ` [bug#54644] [PATCH 3/7] gnu: rust-located-yaml 0.2: Update to 0.2.1 Evgenii Lepikhin via Guix-patches via
2022-03-30 21:35 ` [bug#54644] [PATCH 4/7] gnu: rust-minimal-lexical " Evgenii Lepikhin via Guix-patches via
2022-03-31 11:59 ` Maxime Devos
2022-03-31 12:01 ` Maxime Devos
2022-03-31 14:47 ` Efraim Flashner
2022-03-31 15:40 ` Maxime Devos
2022-03-31 22:30 ` Evgenii Lepikhin via Guix-patches via
2022-04-01 6:38 ` Maxime Devos [this message]
2022-04-01 13:51 ` Evgenii Lepikhin via Guix-patches via
2022-04-01 15:32 ` Maxime Devos
2022-03-30 21:36 ` [bug#54644] [PATCH 5/7] gnu: rust-nom 7.1: Update to 7.1.1 Evgenii Lepikhin via Guix-patches via
2022-03-30 21:37 ` [bug#54644] [PATCH 6/7] gnu: rust-serde-regex 1: Update to 1.1.0 Evgenii Lepikhin via Guix-patches via
2022-03-31 11:56 ` Maxime Devos
2022-03-31 19:16 ` Maxime Devos
2022-03-31 11:58 ` Maxime Devos
2022-03-31 14:48 ` Efraim Flashner
2022-03-30 21:37 ` [bug#54644] [PATCH 7/7] gnu: Add copyright for myself Evgenii Lepikhin via Guix-patches via
2022-04-01 21:54 ` [bug#54644] [PATCH v2 1/6] gnu: rust-nom-locate-4: Add 4.0.0 Evgenii Lepikhin via Guix-patches via
2022-04-01 21:54 ` [bug#54644] [PATCH v2 2/6] gnu: rust-pretty 0.11: Update to 0.11.2 Evgenii Lepikhin via Guix-patches via
2022-04-01 21:54 ` [bug#54644] [PATCH v2 3/6] gnu: rust-located-yaml: Add 0.2.1 Evgenii Lepikhin via Guix-patches via
2022-04-01 21:54 ` [bug#54644] [PATCH v2 4/6] gnu: rust-nom 7: Update to 7.1.1 Evgenii Lepikhin via Guix-patches via
2022-04-01 21:54 ` [bug#54644] [PATCH v2 5/6] gnu: rust-serde-regex: Add 1.1.0 Evgenii Lepikhin via Guix-patches via
2022-04-01 21:54 ` [bug#54644] [PATCH v2 6/6] Add copyright for myself Evgenii Lepikhin via Guix-patches via
2022-05-16 13:49 ` [bug#54644] [PATCH v2 1/6] gnu: rust-nom-locate-4: Add 4.0.0 Evgenii Lepikhin via Guix-patches via
2022-05-30 8:18 ` bug#54644: " Efraim Flashner
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=1869e46d2f4e4081ec985d1c48d1bf702ecf38e5.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=54644@debbugs.gnu.org \
--cc=e.lepikhin@corp.mail.ru \
--cc=efraim@flashner.co.il \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).