all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Jonas Møller" <jonas@moesys.no>, 62064@debbugs.gnu.org
Subject: bug#62064: Why is only rust-1.60 exported when 1.65 is defined?
Date: Mon, 03 Apr 2023 16:03:09 +0200	[thread overview]
Message-ID: <87wn2tf4gy.fsf@gmail.com> (raw)
In-Reply-To: <587407cb-5045-2c86-cf9b-6d331c8bc1b3@moesys.no>

Hi,

On mar., 14 mars 2023 at 08:59, Jonas Møller via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:

> 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`" 

Using your proposal, how do you deal with

    guix install rust rust-foobar

?  Do you expect that rust-foobar is built using the latest Rust or the
internal Rust?

Well, from my point of view, what you would like is that the symbol
’rust-1.65’ would be named “rust-next”.  It is the current way for
several versions; see emacs vs emacs-next.

See https://issues.guix.gnu.org/62643

I propose to close this report once #62643 is merged.

Cheers,
simon




  reply	other threads:[~2023-04-03 17:37 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 [this message]
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=87wn2tf4gy.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=62064@debbugs.gnu.org \
    --cc=jonas@moesys.no \
    /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.