all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nikolai Merinov <nikolai.merinov@member.fsf.org>
To: "Ludovic Courtès" <ludo@gnu.org>,
	"Danny Milosavljevic" <dannym@scratchpost.org>
Cc: 30831@debbugs.gnu.org
Subject: [bug#30831] [PATCH] gnu: rust: Update rust from 1.22.1 release to 1.24.1
Date: Mon, 19 Mar 2018 17:26:07 +0500	[thread overview]
Message-ID: <87h8pcckv4.fsf@member.fsf.org> (raw)
In-Reply-To: <87bmfmmm78.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 17 Mar 2018 22:22:35 +0100")

Hi Ludovic,

> Instead of incrementing the version number of the bootstrap binaries, do
> you think it would be an option to keep 1.22 and build 1.23 from it, or
> does that cargo/rust merge prevent it?

In rust 1.22 there already was possibility to build "cargo" from "rust"
repository, so suggested packages structures change can be used either
for old "rust" releases.

By default rust should be built with
https://github.com/rust-lang/rust/blob/1.24.1/src/stage0.txt versions of
rust and cargo. In most of cases this for "1.X.Y" release it want to use
"1.(X-1).0" version of rustc and "0.X.0" version of cargo. As result to
build release version of Rust compiler we should have previous release
of rust compiler.

Actually there is two ways to achieve this:
1. Constantly update bootsrap binaries version.
2. For each new release create new package. As result we'll be able to
use old rust release to build each new rust release. E.g. we can use
1.21.0 bootstrap binaries, then build 1.22.0 rust and use it to build
1.23.0 rust and then use it to build 1.24.1 rust.

Which way is preferable? 

Please do not merge my patch until I'll check Danny's report about
reproducability.

Regards,
Nikola

  reply	other threads:[~2018-03-19 12:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-13 19:06 [bug#30831] [PATCH] gnu: rust: Update rust from 1.22.1 release to 1.24.1 Nikolai Merinov
2018-03-17 21:22 ` Ludovic Courtès
2018-03-19 12:26   ` Nikolai Merinov [this message]
2018-03-19 16:23     ` Ludovic Courtès
2018-03-20 10:56       ` Ricardo Wurmus
2018-03-22 21:01         ` Nikolai Merinov
2018-03-27  7:41           ` Ludovic Courtès
2018-03-27 12:56             ` Nikolai Merinov
2018-03-27 13:19               ` Danny Milosavljevic
2018-03-27 18:08                 ` Marius Bakke
2018-03-27 19:56                   ` Ricardo Wurmus
2018-03-30 23:51                   ` Danny Milosavljevic
2018-03-27 13:09             ` Danny Milosavljevic
2018-03-18 18:58 ` Danny Milosavljevic
2018-03-21 19:02   ` Nikolai Merinov
2018-03-24 16:26     ` Danny Milosavljevic
2018-03-27 13:02       ` Nikolai Merinov
2018-03-30 13:48         ` bug#30831: " Danny Milosavljevic
2018-03-22  7:20 ` [bug#30831] building rust on aarch64 Efraim Flashner

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=87h8pcckv4.fsf@member.fsf.org \
    --to=nikolai.merinov@member.fsf.org \
    --cc=30831@debbugs.gnu.org \
    --cc=dannym@scratchpost.org \
    --cc=ludo@gnu.org \
    /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.