unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: "(" <paren@disroot.org>, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 62643@debbugs.gnu.org, Simon Tournier <zimon.toutoune@gmail.com>
Subject: [bug#62643] [PATCH] gnu: rust-1.65: Rename package to rust-next.
Date: Mon, 03 Apr 2023 23:08:49 +0300	[thread overview]
Message-ID: <10249735.nUPlyArG6x@pbp> (raw)
In-Reply-To: <87pm8kd94r.fsf_-_@gmail.com>

On Monday, 3 April 2023 23:05:24 IDT Maxim Cournoyer wrote:
> Hi,
> 
> "(" <paren@disroot.org> writes:
> > Hi Simon,
> > 
> > On Mon Apr 3, 2023 at 3:00 PM BST, Simon Tournier wrote:
> >> * gnu/packages/rust.scm (rust-next): New exported variable, formerly
> >> known as "rust-1.65".
> > 
> > For the reasons I outlined in <https://issues.guix.gnu.org/62064#5>, we
> > can't just export RUST-1.65 as RUST-NEXT, unfortunately...
> 
> Agreed.  If there is a need for newer public rust version, please go
> through the maintainers' note above the 'rust' variable:
> 
> ;;; 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.
> 
> Usually the whole collection keeps building with the latest rust version
> as it's backward compatible, I think, so it's not as much work as it may
> look like.
> 
> OK to close?

I'd rather work on upgrading the whole rust ecosystem packaged in Guix than 
keep a newer version of rust working while fielding questions about why it's 
not yet the default.







  reply	other threads:[~2023-04-03 20:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03 14:00 [bug#62643] [PATCH] gnu: rust-1.65: Rename package to rust-next Simon Tournier
2023-04-03 18:13 ` ( via Guix-patches via
2023-04-03 20:05   ` Maxim Cournoyer
2023-04-03 20:08     ` Efraim Flashner [this message]
2023-04-03 20:51     ` Simon Tournier
2023-04-04  3:49       ` Maxim Cournoyer
2023-04-03 20:53     ` Simon Tournier
2023-04-04  3:53       ` Maxim Cournoyer
2023-04-04  7:47         ` Simon Tournier

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=10249735.nUPlyArG6x@pbp \
    --to=efraim@flashner.co.il \
    --cc=62643@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=paren@disroot.org \
    --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).