From: "Jonas Møller via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: 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, 04 Apr 2023 11:53:18 +0000 [thread overview]
Message-ID: <TKJlgTQi1msg3FvFQ1QLOfkYMrKhELY_Ta85j2dcVG8x_h7st9R5x3Gi1hLdIcnJsnscLuUqoJPlyxP_rt8dAXEojD6Hdi6W5q7VF6bKDV4=@moesys.no> (raw)
In-Reply-To: <87wn2tf4gy.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
Yes, rust-next works, but I was imagining renaming the current rust to something like default-rust-build, then defining a new ‘rust’ which will be continuously updated to the latest version of rust.
I think a user centric design would name the latest rust as just ‘rust’, while letting the package-manager implementation detail have the longer name.
Mvh Jonas Møller
On Mon, Apr 3, 2023 at 16:03, Simon Tournier <zimon.toutoune@gmail.com> wrote:
> 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
[-- Attachment #2: Type: text/html, Size: 1855 bytes --]
next prev parent reply other threads:[~2023-04-04 11:54 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 [this message]
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
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='TKJlgTQi1msg3FvFQ1QLOfkYMrKhELY_Ta85j2dcVG8x_h7st9R5x3Gi1hLdIcnJsnscLuUqoJPlyxP_rt8dAXEojD6Hdi6W5q7VF6bKDV4=@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 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).