From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45667) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f0uiR-0005Oj-BO for guix-patches@gnu.org; Tue, 27 Mar 2018 15:57:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f0uiM-0006e4-Gd for guix-patches@gnu.org; Tue, 27 Mar 2018 15:57:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:48374) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1f0uiM-0006dT-9R for guix-patches@gnu.org; Tue, 27 Mar 2018 15:57:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1f0uiL-0000jh-Q5 for guix-patches@gnu.org; Tue, 27 Mar 2018 15:57:01 -0400 Subject: [bug#30831] [PATCH] gnu: rust: Update rust from 1.22.1 release to 1.24.1 Resent-Message-ID: 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> <87in9iynhq.fsf@gnu.org> <87zi2the25.fsf@member.fsf.org> <20180327151942.1458e82c@scratchpost.org> <87h8p1gzni.fsf@fastmail.com> From: Ricardo Wurmus In-reply-to: <87h8p1gzni.fsf@fastmail.com> Date: Tue, 27 Mar 2018 21:56:12 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID: <87k1txfg2r.fsf@elephly.net> 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: Marius Bakke Cc: 30831@debbugs.gnu.org Marius Bakke writes: >> (What Mozilla recommends is we compile Rust1, use Rust2 to compile Rust3= , use >> Rust3 to compile Rust4, likewise for each new release) > > I think we should heed upstreams advice in that case. A long bootstrap > chain is really only a problem during 'core-updates', no? It=E2=80=99s a problem for people building from source and it makes for a brittle bootstrap because any of the packages could break. Having a long bootstrap chain to debug on core-updates is no fun =E2=80=94 I=E2=80= =99m saying this as someone who has just fixed problems in the relatively simple bootstrap chain for Java. > IIUC mrustc only targets x86_64 currently, so I don't expect it to > become viable for Guix in a good while. This is a problem, but I do hope that eventually we will be able to use mrust to bypass an ever-growing chain. -- Ricardo