From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59611) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f0jF8-0001ES-DA for guix-patches@gnu.org; Tue, 27 Mar 2018 03:42:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f0jF4-0005nw-Ej for guix-patches@gnu.org; Tue, 27 Mar 2018 03:42:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:47198) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1f0jF4-0005nk-BE for guix-patches@gnu.org; Tue, 27 Mar 2018 03:42:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1f0jF4-0000lo-4F for guix-patches@gnu.org; Tue, 27 Mar 2018 03:42:02 -0400 Subject: [bug#30831] [PATCH] gnu: rust: Update rust from 1.22.1 release to 1.24.1 Resent-Message-ID: From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) References: <874llhdocu.fsf@member.fsf.org> <87bmfmmm78.fsf@gnu.org> <87h8pcckv4.fsf@member.fsf.org> <87efkgvxt1.fsf@gnu.org> <87o9jjc8xg.fsf@elephly.net> <87y3ij25bf.fsf@member.fsf.org> Date: Tue, 27 Mar 2018 09:41:05 +0200 In-Reply-To: <87y3ij25bf.fsf@member.fsf.org> (Nikolai Merinov's message of "Fri, 23 Mar 2018 02:01:08 +0500") Message-ID: <87in9iynhq.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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: Nikolai Merinov Cc: Ricardo Wurmus , 30831@debbugs.gnu.org Hello Nikolai, Nikolai Merinov skribis: > Ricardo Wurmus writes: > >> Ludovic Court=C3=A8s writes: >> >>> Hello, >>> >>> Nikolai Merinov skribis: >>> >>>> 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?=20 >>> >>> Like I wrote, I would prefer option #2, so as to increase =E2=80=9Cbina= ry >>> diversity=E2=80=9D and not rely on builds made by upstream. >>> >>> This obviously relates to . Ricardo, what= =E2=80=99s >>> your take on this? >> >> I agree. In the long run, however, I=E2=80=99d prefer for Rust to be >> bootstrapped through one of the alternative implementations. Then we >> don=E2=80=99t need to keep a long chain of older versions. >> >> Currently, however, I don=E2=80=99t see a way around it. > > Hi, I prepared proof-of-concept solution with rust-bootstrap frozed on > 1.22.1 release. Would it be an option to stick to 1.21? Or is it already too difficult? (Apologies if this was already answered previously.) I=E2=80=99m asking be= cause I wonder how big the temptation will be to upgrade =E2=80=98rust-bootstrap= =E2=80=99 again next time. > Do you think suggested code with "split all code to small steps and > remove fixed issues in new releases" is correct way to provide series > of releases? Or it will be better to copy builder code to state it > directly that this specific modification is tested on each rust > release? I=E2=80=99m not sure what you mean. Danny, you probably have more experience than I do with Rust. :-) Thoughts? Thanks, Ludo=E2=80=99.