all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jonas Møller via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: Simon Tournier <zimon.toutoune@gmail.com>, 62064@debbugs.gnu.org
Subject: bug#62064: Why is only rust-1.60 exported when 1.65 is defined?
Date: Tue, 14 Mar 2023 08:59:09 +0000	[thread overview]
Message-ID: <587407cb-5045-2c86-cf9b-6d331c8bc1b3@moesys.no> (raw)
In-Reply-To: <864jqn91hw.fsf@gmail.com>

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

I think it's fine for Guix to use a specific version of Rust internally, and to be conservative about updating that.

But Guix becomes unsuitable for anyone developing software in Rust, if this technical detail in the package manager means that they can't use newer versions of the toolchain.

I think it would be best if Guix separated these concerns, by disconnecting the "Rust we use to build packages internally" with the "Rust that gets installed with `guix install rust`"

— Mvh Jonas Møller

[-- Attachment #2: Type: text/html, Size: 798 bytes --]

  reply	other threads:[~2023-03-14  9:00 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 [this message]
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

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=587407cb-5045-2c86-cf9b-6d331c8bc1b3@moesys.no \
    --to=bug-guix@gnu.org \
    --cc=62064@debbugs.gnu.org \
    --cc=jonas@moesys.no \
    --cc=zimon.toutoune@gmail.com \
    /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.