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: Tue, 14 Mar 2023 09:32:43 +0100 [thread overview]
Message-ID: <864jqn91hw.fsf@gmail.com> (raw)
In-Reply-To: <66be3bb1-5adb-4e6b-f050-6159da88124e@moesys.no>
Hi Jonas,
On Mon, 13 Mar 2023 at 20:59, Jonas Møller via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:
>> 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).
>
> Rust has very strong stability guarantees between 1.x releases, and
> has a very extensive set of tooling/infrastructure to make sure no
> breaking changes make their way into a release (see crater [1]). Any
> Rust-based package big enough to be packaged by Guix will have had its
> test-suite confirmed to work with the new release of cargo/rustc long
> before any new release is made (and in many cases before pull-requests
> are merged.)
To test your claim, I would suggest to write a manifest using package
transformations [1] and then rebuild all Rust packages from Guix.
1: https://guix.gnu.org/manual/devel/en/guix.html#Package-Transformation-Options
2: https://guix.gnu.org/manual/devel/en/guix.html#Defining-Package-Variants
> Nevertheless, rebuilding all Rust packages on every rustc release
> isn't strictly necessary. (Improvements in optimizations do happen,
> but they are mosty minor release-to-release.)
I do not understand how this could be implemented with Guix. Could you
be more specific?
Well, all in all, I do not think this report is a bug but a wish list.
Instead, I would suggest to discuss the actionable tasks for updating
Rust [3] in the mailing list guix-devel, WDYT?
3: https://guix.gnu.org/manual/devel/en/guix.html#Defining-Package-Variants
Cheers,
simon
next prev parent reply other threads:[~2023-03-14 8:47 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=864jqn91hw.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.