From: ludo@gnu.org (Ludovic Courtès)
To: Nikolai Merinov <nikolai.merinov@member.fsf.org>
Cc: Ricardo Wurmus <rekado@elephly.net>, 30831@debbugs.gnu.org
Subject: [bug#30831] [PATCH] gnu: rust: Update rust from 1.22.1 release to 1.24.1
Date: Tue, 27 Mar 2018 09:41:05 +0200 [thread overview]
Message-ID: <87in9iynhq.fsf@gnu.org> (raw)
In-Reply-To: <87y3ij25bf.fsf@member.fsf.org> (Nikolai Merinov's message of "Fri, 23 Mar 2018 02:01:08 +0500")
Hello Nikolai,
Nikolai Merinov <nikolai.merinov@member.fsf.org> skribis:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> 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.
>
> 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’m asking because
I wonder how big the temptation will be to upgrade ‘rust-bootstrap’
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’m not sure what you mean.
Danny, you probably have more experience than I do with Rust. :-)
Thoughts?
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-03-27 7:42 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
2018-03-22 21:01 ` Nikolai Merinov
2018-03-27 7:41 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87in9iynhq.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30831@debbugs.gnu.org \
--cc=nikolai.merinov@member.fsf.org \
--cc=rekado@elephly.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.