all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ROCKTAKEY <rocktakey@gmail.com>
To: 62064@debbugs.gnu.org
Subject: bug#62064: Why is only rust-1.60 exported when 1.65 is defined?
Date: Sat, 25 Mar 2023 00:41:31 +0900	[thread overview]
Message-ID: <a9e535e1-501d-2c35-f2a6-8a3156084734@gmail.com> (raw)
In-Reply-To: <0f93d56a-f744-b7c6-2be6-2dcf7fe08741@moesys.no>

Hi,

Some of cargo packages require rust-1.61 or higher. Currently, there is 
no way to build them with Guix because of this issue.

So I think cargo-build-system (and other build-systems?) should be able 
to specify the version of rust. As of now, it accepts #:rust keyword, 
but there is no package to pass it to (because the packages named 
rust-1.* are not public).

Providing newer Rust packages are needed in this regard as well.

ROCKTAKEY





      parent reply	other threads:[~2023-03-26 20:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 16:09 bug#62064: Why is only rust-1.60 exported when 1.65 is defined? Jonas Møller via Bug reports for GNU Guix
2023-03-12 14:14 ` Matthew James Kraai
2023-03-13 13:36 ` Greg Hogan
2023-03-13 14:32 ` Simon Tournier
2023-03-13 20:59   ` Jonas Møller via Bug reports for GNU Guix
2023-03-14  8:32     ` Simon Tournier
2023-03-14  8:59       ` Jonas Møller via Bug reports for GNU Guix
2023-04-03 14:03         ` Simon Tournier
2023-04-04 11:53           ` Jonas Møller via Bug reports for GNU Guix
2023-03-13 21:11 ` paren--- via Bug reports for GNU Guix
2023-04-04  9:30   ` Simon Tournier
2024-01-22  5:02     ` Maxim Cournoyer
2023-03-24 15:41 ` ROCKTAKEY [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=a9e535e1-501d-2c35-f2a6-8a3156084734@gmail.com \
    --to=rocktakey@gmail.com \
    --cc=62064@debbugs.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.