From: Marius Bakke <mbakke@fastmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>,
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 20:08:01 +0200 [thread overview]
Message-ID: <87h8p1gzni.fsf@fastmail.com> (raw)
In-Reply-To: <20180327151942.1458e82c@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]
Danny Milosavljevic <dannym@scratchpost.org> writes:
> 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 glance.
>
> 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 know
> that Rust upstream likes to do this chain of Rust1 -> Rust2 -> Rust3 -> Rust4
> 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 just
> 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, 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?
IIUC mrustc only targets x86_64 currently, so I don't expect it to
become viable for Guix in a good while.
> [1] https://github.com/thepowersgang/mrustc
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-03-27 18:09 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
2018-03-27 12:56 ` Nikolai Merinov
2018-03-27 13:19 ` Danny Milosavljevic
2018-03-27 18:08 ` Marius Bakke [this message]
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=87h8p1gzni.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=30831@debbugs.gnu.org \
--cc=dannym@scratchpost.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.