From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58928) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f0oWE-0002mY-G6 for guix-patches@gnu.org; Tue, 27 Mar 2018 09:20:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f0oWA-000755-Gu for guix-patches@gnu.org; Tue, 27 Mar 2018 09:20:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:47428) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1f0oWA-00074t-E3 for guix-patches@gnu.org; Tue, 27 Mar 2018 09:20:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1f0oWA-00069W-6l for guix-patches@gnu.org; Tue, 27 Mar 2018 09:20:02 -0400 Subject: [bug#30831] [PATCH] gnu: rust: Update rust from 1.22.1 release to 1.24.1 Resent-Message-ID: Date: Tue, 27 Mar 2018 15:19:42 +0200 From: Danny Milosavljevic Message-ID: <20180327151942.1458e82c@scratchpost.org> In-Reply-To: <87zi2the25.fsf@member.fsf.org> 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> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/rsfc9yfJEYkeE74Nv5I6oyJ"; protocol="application/pgp-signature" 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 --Sig_/rsfc9yfJEYkeE74Nv5I6oyJ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Nikolai, I think the incremental (first) version is the best one since you can see which bugs are worked around by us and which are fixed per release at a gla= nce. But really it doesn't matter much which. > Second solution looks too verbose for me, but with first solution on > long chain of versions it will be very hard to manage which changes we > have in newest package. I hope we won't have a long chain of cumulative Rust versions in Guix. I k= now that Rust upstream likes to do this chain of Rust1 -> Rust2 -> Rust3 -> Rus= t4 but that's not really scalable - especially since even one Rust takes a day to compile. We should try to get mrust [1] to work and use it to compile j= ust the newest Rust. If it doesn't work we can still fall back to one of the other ways later. (What Mozilla recommends is we compile Rust1, use Rust2 to compile Rust3, u= se Rust3 to compile Rust4, likewise for each new release) [1] https://github.com/thepowersgang/mrustc --Sig_/rsfc9yfJEYkeE74Nv5I6oyJ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAlq6RO4ACgkQ5xo1VCww uqVCfAf9FqgJxnJQF6QOHw85G7kwDVFXnMhg1CiUgYRe1O5PNcMjCt649kBsuqM0 cV77yVX1TLd2I77PAAxMWpLGtddQQuRZBsmatGitECqExX0kMIdMJWHClGWIhq6P wIuCZISh/Vm4U+HG3hGvE0/9ovTh5B40cQwG+2pAS4Gpu++PqqA0V+YxwOAcWoJe O0il4nM/cv8ufipbkp11orWQGHZkkxAIDdgHKo/RR/SIsG5h7DrdM8Fdym5/vocJ jL5h0/5mpbhXY3Nb7xxJnMoUo6J6h5JzYQeIPE6mkkgNrk3aWwzGMeEj5vczHzqA vmsAkez/1hY0RTKVESPqJSNVFOmrqw== =irAV -----END PGP SIGNATURE----- --Sig_/rsfc9yfJEYkeE74Nv5I6oyJ--