From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43907) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1extsZ-0005vw-Ij for guix-patches@gnu.org; Mon, 19 Mar 2018 08:27:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1extsU-0004VH-LI for guix-patches@gnu.org; Mon, 19 Mar 2018 08:27:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:32922) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1extsU-0004VB-Ff for guix-patches@gnu.org; Mon, 19 Mar 2018 08:27:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1extsU-0007gW-8h for guix-patches@gnu.org; Mon, 19 Mar 2018 08:27:02 -0400 Subject: [bug#30831] [PATCH] gnu: rust: Update rust from 1.22.1 release to 1.24.1 Resent-Message-ID: From: Nikolai Merinov References: <874llhdocu.fsf@member.fsf.org> <87bmfmmm78.fsf@gnu.org> Date: Mon, 19 Mar 2018 17:26:07 +0500 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") Message-ID: <87h8pcckv4.fsf@member.fsf.org> MIME-Version: 1.0 Content-Type: text/plain List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= , Danny Milosavljevic Cc: 30831@debbugs.gnu.org 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