all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Mekeor Melire <mekeor@posteo.de>, 54509@debbugs.gnu.org
Subject: [bug#54509] bump: make rust-cargo understand rust-edition2021 which rustc already does
Date: Thu, 30 Jun 2022 10:10:05 +0200	[thread overview]
Message-ID: <eb52fedfbd9ce41ba736c348030092f4335d70f0.camel@telenet.be> (raw)
In-Reply-To: <87bkub5b4l.fsf@posteo.de>

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

Mekeor Melire schreef op wo 29-06-2022 om 22:57 [+0000]:
> the rust-compiler which is packaged for guix supports edition2021
> but the cargo version packaged for guix does not

Pretty sure that it does, IIRC under antioxidant-build-system I've seen
some things being compiled with the 2021 edition of rust, presumably
they also compiled under cargo-build-system.

Also, rust-cargo does not have the cargo binary (but a cargo library!),
you may be looking for the 'cargo' output of the 'rust' package
instead.

Greetings,
Maxime.

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

  reply	other threads:[~2022-06-30  8:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 17:46 [bug#54509] rust-cargo: Update to 0.60.0 to support Edition2021 projects Paul Alesius
2022-03-21 18:46 ` Maxime Devos
2022-03-21 20:59   ` Paul Alesius
2023-02-09 13:18     ` bug#54509: " Maxim Cournoyer
2022-06-29 22:57 ` [bug#54509] bump: make rust-cargo understand rust-edition2021 which rustc already does Mekeor Melire
2022-06-30  8:10   ` Maxime Devos [this message]
2022-07-01 21:48     ` Mekeor Melire
2022-07-02 11:27       ` Tobias Geerinckx-Rice via Guix-patches via
2022-07-02 11:35         ` Tobias Geerinckx-Rice via Guix-patches via
2022-07-06 14:06           ` Mekeor Melire

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=eb52fedfbd9ce41ba736c348030092f4335d70f0.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=54509@debbugs.gnu.org \
    --cc=mekeor@posteo.de \
    /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.