unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 32834@debbugs.gnu.org
Subject: [bug#32834] [PATCH] gnu: icecat: Build with rust-1.24.
Date: Sat, 29 Sep 2018 23:20:48 -0400	[thread overview]
Message-ID: <87wor34qnj.fsf@netris.org> (raw)
In-Reply-To: <20180930005515.6860d2a4@scratchpost.org> (Danny Milosavljevic's message of "Sun, 30 Sep 2018 00:55:15 +0200")

Danny Milosavljevic <dannym@scratchpost.org> writes:

> On Sat, 29 Sep 2018 23:55:36 +0200
> ludo@gnu.org (Ludovic Courtès) wrote:
>
>> Hi Efraim,
>> 
>> Efraim Flashner <efraim@flashner.co.il> skribis:
>> 
>> > * gnu/packages/gnuzilla.scm (icecat)[native-inputs]: Use the oldest
>> > compatable rust over newer releases when building icecat.  
>> 
>> [...]
>> 
>> > +      ;; Icecat 60 checkes for rust>=1.24
>> > +     `(("rust" ,rust-1.24)
>> > +       ("cargo" ,rust-1.24 "cargo")  
>> 
>> I suppose the goal is to reduce the build chain, right?
>> 
>> Mark, Danny: WDYT?
>
> I think it's a good idea.
>
> Eventually, the rust bootchain will change to mrustc -> rust@1.25.0 -> ...,
> but we can cross that bridge when we come to it.
>
> I'm not sure about Rust's policy with regard to CVEs.  Are those patched
> in old releases, too?

Indeed, that's my main concern.  Might the older Rust compilers have
bugs that could lead to security flaws in IceCat?

Here's another possible approach to mitigate the cost of building this
long chain of Rust compilers: perhaps older versions of Rust could use
only minimal and highly stable inputs, such that they would be built
only once per core-updates cycle.  Thoughts?

       Mark

  reply	other threads:[~2018-09-30  3:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25  4:49 [bug#32834] [PATCH] gnu: icecat: Build with rust-1.24 Efraim Flashner
2018-09-29 21:55 ` Ludovic Courtès
2018-09-29 22:55   ` Danny Milosavljevic
2018-09-30  3:20     ` Mark H Weaver [this message]
2018-09-30 19:27       ` Ludovic Courtès
2018-09-30  5:44   ` Efraim Flashner
2018-10-01  9:03     ` Nils Gillmann
2018-10-02  9:16       ` Ludovic Courtès
2018-10-02  9:47         ` Nils Gillmann
2018-10-03  3:48           ` Joe Hillenbrand
2018-10-09  0:18           ` Mark H Weaver
2018-10-14  6:59             ` bug#32834: " 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=87wor34qnj.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=32834@debbugs.gnu.org \
    --cc=dannym@scratchpost.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).