unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 30831@debbugs.gnu.org
Subject: [bug#30831] [PATCH] gnu: rust: Update rust from 1.22.1 release to 1.24.1
Date: Tue, 20 Mar 2018 11:56:11 +0100	[thread overview]
Message-ID: <87o9jjc8xg.fsf@elephly.net> (raw)
In-Reply-To: <87efkgvxt1.fsf@gnu.org>


Ludovic Courtès <ludo@gnu.org> writes:

> Hello,
>
> Nikolai Merinov <nikolai.merinov@member.fsf.org> 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? 
>
> Like I wrote, I would prefer option #2, so as to increase “binary
> diversity” and not rely on builds made by upstream.
>
> This obviously relates to <http://bootstrappable.org/>.  Ricardo, what’s
> your take on this?

I agree.  In the long run, however, I’d prefer for Rust to be
bootstrapped through one of the alternative implementations.  Then we
don’t need to keep a long chain of older versions.

Currently, however, I don’t see a way around it.

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  reply	other threads:[~2018-03-20 10:58 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
2018-03-19 16:23     ` Ludovic Courtès
2018-03-20 10:56       ` Ricardo Wurmus [this message]
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o9jjc8xg.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=30831@debbugs.gnu.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).