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, 13 Mar 2023 15:32:23 +0100 [thread overview]
Message-ID: <873568lo20.fsf@gmail.com> (raw)
In-Reply-To: <0f93d56a-f744-b7c6-2be6-2dcf7fe08741@moesys.no>
Hi,
On mer., 08 mars 2023 at 16:09, Jonas Møller via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:
>> ;;; Note: Only the latest versions of Rust are supported and tested. The
>> ;;; intermediate rusts are built for bootstrapping purposes and should not
>> ;;; be relied upon. This is to ease maintenance and reduce the time
>> ;;; required to build the full Rust bootstrap chain.
>> ;;;
>> ;;; Here we take the latest included Rust, make it public, and re-enable tests
>> ;;; and extra components such as rustfmt.
>
> And then proceeds to define-public rust as rust-1.60, and I was
> wondering if there's any particular reason why a year-old version is
> used rather than the 1.65 version. This seems like a mistake, given
> that the comment claims that the "latest included Rust" should be made
> public.
Well, I know few about Rust and I guess it is because using ’rust-1.65’
as default Rust is a world-rebuild.
--8<---------------cut here---------------start------------->8---
$ guix refresh rust -l | cut -f1 -d':'
Building the following 4560 packages would ensure 6637 dependent packages are rebuilt
--8<---------------cut here---------------end--------------->8---
> This is especially troublesome for Rust on Guix because of both how
> fast its ecosystem moves onto new language/tooling features, and
> because using rustup (the solution for this on other slow-moving
> distros) relies on pre-built executables that don't work
> out-of-the-box on Guix.
Well, the issue when exporting ’rust-1.65’ is that it would possible
incompatible with the Rust packages provided by Guix and compiled with
’rust’ (1.60).
Maybe, one could imagine a package transformation
’package-with-explicit-rust’ as it is done for Python and OCaml.
Cheers,
simon
next prev parent reply other threads:[~2023-03-13 15:03 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 [this message]
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
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=873568lo20.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 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).